🔧 Build Ember Cli Apps on Azure Websites
Shell JavaScript
Latest commit 14b5b40 Feb 9, 2016 @felixrieseberg Merge pull request #16 from m-gagne/Issue15
Issue #15: $NODE_EXE not escaped in deploy.sh:119
Permalink
Failed to load latest commit information.
bin
.gitignore
LICENSE
README.md
package.json

README.md

Continuous Deployment of Ember Cli Apps with Azure Websites

This Node Module enables Azure Websites to run ember build (building the Ember Cli app) up in the cloud - and automatically deploy the resulting dist folder to your website.

This is cool because Azure Websites can be automatically hooked up to any Git repository (including GitHub, BitBucket, etc). Together with this module, enabling continuous deployment for your Ember Cli app - simply push a new commit to GitHub and the new version of your website will be live within seconds. For more information, see this blog post. Made with ❤️ by Microsoft.

Installation

For Ember Cli 1.13.8 / 2.x (or newer) the following two commands in your app's root folder:

npm install --save-dev -g ember-cli-azure-deploy
azure-deploy init

If you're running Ember Cli 1.13.7 (or below), please install with:

npm install -g ember-cli-azure-deploy@1.2.5
azure-deploy init

This will create a deploy.sh in your project's root folder, enabling Azure to follow a set of instructions - including installing all the required Node Modules, running ember build and deploying the resulting dist/ folder to your website's wwwroot.

Required Azure Machines

Please note that Ember Cli is pretty resource hungry - just installing all the required default packages eats up a full gigabyte of memory. If you're experiencing randomly crashing installs or builds, try increasing the size of your web app.

Reporting Issues

If you run into any trouble, please do report it. To get the latest log of what actually went wrong, visit the Azure Management Portal, go to your website, and select 'Deployments'. Each deployment will have its own log, even if failed.

To take a look at the file system (and get a PowerShell / CMD on your website), visit http://YOUR_WEBSITE.scm.azurewebsites.net. You will also find logs there.