You have two dedicated small-size servers running Windows Server and PHP 5.5. They will auto scale to a max of 4 servers if there is a lot of load. One backup occurs each day at 1am.

 

Any changes to the ftp size will be replicated to all active servers. You have the option of running scheduled jobs should you ever need it. Finally, I can give you a deployment slot to stage your changes before moving them to production.

 

FTP login name: peoples\mbxftp3030

FTP password: cha*cha#cha0303

 FTP HOST NAME

ftp://waws-prod-blu-003.ftp.azurewebsites.windows.net

FTPS HOST NAME

ftps://waws-prod-blu-003.ftp.azurewebsites.windows.net

FTP DIAGNOSTIC LOGS

ftp://waws-prod-blu-003.ftp.azurewebsites.windows.net/LogFiles

FTPS DIAGNOSTIC LOGS

ftps://waws-prod-blu-003.ftp.azurewebsites.windows.net/LogFiles



You now have a staging deployment slot. How it works: http://azure.microsoft.com/en-us/documentation/articles/web-sites-staged-publishing/

 

http://peoples-staging.azurewebsites.net

ftp username: peoples__Staging\mbxftp3030

 

all other ftp info is the same.

 

I created a staging slot for you but you have to be an Azure admin do the swap. That sucks because there is only one level of azure access: god. And we can’t make everyone god J. Hopefully Microsoft will implement finer grain security soon.

 

I can push the swap button for you (or Manny, Javier, Jaime).