Deploying EE on Azure
How Do I?
Hi there,
i’m wondering if EE (latest version - Open Source one) can be deployed to Azure as a PaaS Service. with knowing that the case here we use EE as a portal for CMS it contains more that 200 websites in a sub-domains like (SharePoint) i mean that we have 1 parent website and around 200 websites as a childs for that parent inherits everything from it.
thanks for advance
I’ve deployed it to Azure and seems to be fine. However, I’m using the MySQL in app for a app service and because mysql is on a non-standard port i’m unable to complete the setup process
admin.php just says that localhost is not a valid server. Same with 127.0.0.1
Is there anyway to properly specify a port number in that field?
I’m doing the same thing. Took me forever to figure out the secret to getting mysql in app to work with EE 1.7.4. Here’s a starting point.
-you MUST turn off strict mode for mysql. It’s a bit tricky.
From within the Azure portal, go to Application Settings.
Add new setting.
Under ‘app setting name’ put “WEBSITE_MYSQL_ARGUMENTS”.
Under ‘value’ put “–sql_mode=NO_ENGINE_SUBSTITUTION”.
Leave out the quotation marks
-The sql database password is going to change at random, due to how microsoft manages the mysql in app functionality. You can find the connection string within the file structure at /data/mysql/MYSQLCONNSTR_localdb.txt. It’ll show something like: Database=localdb;Data Source=127.0.0.1:56431;User Id=whateveritsays;Password=whateveritsays. so in this case, 127.0.0.1 would not work for a server name, but 127.0.0.1:56431 will work just fine.
I currently have those server values placed in my config.php file and they’re working fine, but apparently you’re supposed to use some scripts to read that particular file instead of simply imputing static values so that you’ll stay connected when the port or password change (not sure how often it’s supposed to happen). More info can be found here. https://blogs.msdn.microsoft.com/appserviceteam/2016/08/18/announcing-mysql-in-app-preview-for-web-apps/
Another thing to watch out for, is that when you go to ‘mysql in app’ from the azure portal and click ‘manage’, you may get a login screen as opposed to the phpmyadmin interface. If so, simply visit your webpage for about 15 seconds so that the service can actually start up, and THEN revisit the ‘manage’ button. It should then let you right in. (very frustrating trying to figure that bit out. no credentials will work on the login screen)
Now bear in mind, according to the Azure documentation, mysql in app isn’t meant for production environments. I’m not sure just how limited it is, but it’s been a great staging ground for test environments for me so far.