- Visual Studio 2013
- Windows Management Framework 3.0 download link
- Latest Powershell for Azure (version 0.6.19) download link
- Windows Azure SDK for .NET 2.4. Web Platform Installer download link
- Java Runtime Environment 7. Download link
- Full Source Code package
Execute all commands and scripts in Powershell for Azure.
- Open the PowerShell and type the following command “Get-AzurePublishSettingsFile”. This will open the browser with azure login page. Once logged in, you will be able to download PublishSettings file, which contains information on how to connect to your azure subscription.
- Rename it to VirtoCommerce.PublishSettings and place it to the deploy.ps1 file folder which is in \VirtoCommerce.Source\src\Extensions\Setup\VirtoCommerce.PowerShell\
- Open your azure management portal.
- Create new database server and create database in it.
Select "New SQL database server" and select the closest geografically server in the next step as this has impact on deployment speed. If the server response won't be quick enough you may get timeout errors during database deployment process. You can check which of the servers response is the best here
Remember entered credentials as you will need them to enter later in the deploy.ps1 script.
- Add your current ip to the firewall (in the azure management portal).
- Run Set-ExecutionPolicy RemoteSigned command in PowerShell.
- Open the deploy.ps1 script and set the variables values as described in comments to each variable
- Run the deploy.ps1 script. Sit back and relax as the deployment script will compile the solution, create 3 deployment packages (frontend, scheduler and search), create storage account in azure, create and populate database and create 3 services. The progress depends on connection speed and selected server but will normally take about 20-30 minutes.
The final result should look like on the screenshot below.
After script completes, you will be able to browse Virto Commerce frontend deployed on azure.
Open the URL http://-www.cloudapp.net where is your service prefix value entered in the deploy.ps1 script.