How to run “grunt build” during Heroku deployment (angular and ruby-on-rails app)
I’d like to deploy an angular+rails app on Heroku. The app is built off Emmanual Oda’s example code, and compiles its assets using Grunt.
Instead of compiling my assets locally and then committing them to git, I’d prefer to compile them on Heroku. That is, I’d like to run
grunt build on Heroku automatically whenever my app is deployed.
- Ruby version change on heroku push
- How to restore git master, which was replaced by another master
- rake db:reset ignores changes to migration
- Push to heroku from another local branch
- How to get a particular branch of github project in one line command
- Capistrano 3 pulling command line arguments
Does anyone know how I can configure Heroku to do this?
I know server side asset compilation is possible with Node.js apps, for example using mbuchetics’ fork of the heroku nodejs buildpack. When I follow the instructions at that site and push to Heroku, though, I get the following error
-----> Fetching custom git buildpack... done ! Push rejected, no Cedar-supported app detected
For the time being I’m deploying using a Rake task that runs
grunt build locally.
task :deploy do system("rm -rf ./public/*") # empty the public directory system("cd ngapp; grunt build") # make a bogus manifest file to turn off asset compilation on heroku # see here: https://devcenter.heroku.com/articles/rails-asset-pipeline system("mkdir public/assets; touch public/assets/manifest-098f6bcd4621d373cade4e832627b4f6.json") system("git add public/") system("git commit -m \"deploying...\"") system("git push heroku master") end
A server side solution would be preferable!
2 Solutions collect form web for “How to run “grunt build” during Heroku deployment (angular and ruby-on-rails app)”
I believe this is what you want: http://www.angularonrails.com/deploy-angular-rails-single-page-application-heroku/
This solution uses multi buildpacks to run
grunt build in production. No build artifacts in version control.
My project is also based off of that sample rails app structure. May I ask why you want heroku to compile your grunt build rather than committing it? Having heroku compile it means even longer deploy times. What I do is I have a deploy script run grunt build and also run all the tests before committing to a build branch. That build branch is pushed to heroku. That way my development branch stays clean without the compiled assets in the public folder.