This buildpack's purpose is to install node and ember-cli to enable deploying ember apps as part of another app. Say you've got a Laravel or a Rails app and you need to deploy the ember build to the public files path. This is the buildpack for you. It doesn't configure any webserver instances, just fetches the necessary dependencies and executes the required ember build commands to deploy your emberapp.

Forked from heroku-buildpack-ember-cli.

Typically this will be included as an additional buildpack. So configure your heroku app like normally, then add this top the top of the buildpack list.

$ heroku buildpacks:add --app your-app-name --index 1 https://github.com/imipolexg/heroku-buildpack-ember-builder

You'll need to set a few environment variables fort his to work.

You'll need to specifiy the relative path of your Emberapp within your git repo. So if your emberapp's package.json is stored in resources/emberapp/package.json do:

$ heroku config:set EMBER_ROOT="resources/emberapp"

$ heroku config:set EMBER_ENV=production

Have the buildpack run your own scripts before and after the ember build by creating a hooks/before_hook.sh or hooks/after_hook.sh file in your Ember application root:

$ mkdir -p hooks

For a before build hook edit hooks/before_hook.sh, and for an after build hook, edit hooks/after_hook.sh.

These scripts are sourced by the compile script, not executed, so they don't need the executable bit set. They will 'inherit' all the environment variables set up in the compile script, so read through that if you want to get your bearings.

Sometimes it is necessary to rebuild NPM modules or Bower dependencies from scratch. This can become necessary when updating Ember or EmberCLI midway through a project and cleaning the Bower and NPM caches doesn't always refresh the cache in the Dyno during the next deployment. In those cases, here is a simple and clean way to force a rebuild.

To force a rebuild of NPM modules and Bower dependencies:

heroku config:set REBUILD_ALL=true
git commit -am 'rebuild' --allow-empty
git push heroku master
heroku config:unset REBUILD_ALL

To force a rebuild of just the NPM modules:

heroku config:set REBUILD_NODE_PACKAGES=true
git commit -am 'rebuild' --allow-empty
git push heroku master
heroku config:unset REBUILD_NODE_PACKAGES

To force a rebuild of Bower dependencies:

heroku config:set REBUILD_BOWER_PACKAGES=true
git commit -am 'rebuild' --allow-empty
git push heroku master
heroku config:unset REBUILD_BOWER_PACKAGES

The Ember CLI buildpack caches your NPM and Bower dependencies by default. This is similar to the Heroku Buildpack for Node.js. This makes typical deployments much faster. Note that dependencies like components/ember#canary will not be updated on each deploy.

To purge the cache and reinstall all dependencies, run:

$ heroku plugins:install https://github.com/heroku/heroku-repo.git
$ heroku repo:purge_cache -a APPNAME

Clean your project's dependencies:

$ npm cache clear
$ bower cache clean
$ rm -rf node_modules bower_components
$ npm install --no-optional
$ bower install

Be sure to save any Bower or NPM resolutions. Now, let's build your Ember CLI application locally:

$ ember build

Check your git status and see if that process has made any changes to your application's code. Now, try your Heroku deployment again.

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request

This buildpack is a fork of heroku-buildpack-ember-cli, which made it quite easy to hack this variation up. Thanks to everyone who worked on that.