Skip to end of metadata
Go to start of metadata

Redirection Notice

Icon
There three ways to deploy nopCommerce on Windows Azure

1. FTP. Use this method if you already have a package ready to deploy (no source code). You can published to a local File System then upload the published files through ftp. How to get FTP credentials for azure? you go Azure.com - > My Account -> Management portal -> Choose your website -> go Dashboard -> quick glance. From here you can find the FTP credentials or you can 'Reset your deployment credentials' or 'Download the publish profile'. For new azure portal go portal.azure.com -> browse websites -> navigate to your website -> Proeprties. From here you can find the FTP credentials or you can 'Reset your deployment credentials' or 'Download the publish profile'.

2. Visual Studio - web deploy. You can also deploy directly to azure from visual studio. Download or get the deployment credentials from azure using the above way and setup web deploy profile in visual studio

3. Web platform installer. nopCommerce is available in Azure Web Sites application gallery. So go to Azure portal, click "start, new site, from gallery".  Select nopCommerce from the list of available applications. After you enter your database connection information and click OK, nopCommerce will be ready to launch.

Once the site is deployed you have to install nopCommerce. Please read more about it here ("Installation process").

 

Azure has support for multiple instances since version 3.70. It's great for any application scalability.Now you should not worry whether your site can handle large number of visitors. So what exactly has been done to support multiple instances in Azure and web farms?

  • BLOB storage account support in Windows Azure. Please learn more about storage accounts in Azure here.
    • How to configure: once your BLOB storage is set up in Azure, open your web.config file, find "AzureBlobStorage" element and specify your BLOB storage connection string, container, endpoint.
  • Distributed caching and session management support. Redis has been chosen as a caching server (already available in Azure, Amazon, other cloud hosting companies).
    • How to configure:
      • So first, you have to install and setup Redis. Please find more about how to use Redis in Azure here.
      • Once it’s done we have to configure it in nopCommerce. In order to enable caching in Redis open web.config file. Find "RedisCaching" config element. Set its "Enabled" attribute to "true" and then specify "ConnectionString" pointing your Redis server (configured in the first step).
      • We also have to enable Redis as our distributed session management. Please open web.config file. Find and uncomment "sessionState" element. Specify its attributes (host, accessKey, etc) pointing to your Redis server. Please find more about distributed session support in Azure here.
  • Ensure that our schedule tasks are run on one farm node at a time.
    • How to configure: In order to enable this functionality open web.config file, find "WebFarms" element, and set its "MultipleInstancesEnabled" attribute to "True". If you use Windows Azure Websites (not cloud services), then also set "RunOnAzureWebsites" attribute to "True".
  • No labels