Kumade is a command-line program for deploying to Heroku. It aims to provide most of what you want. Unlike other Heroku deploy gems, it is well-tested.
Development is happening very fast, and the internals are in constant flux. The
public API is constant (e.g.
kumade production will work), but you may have to
rebase against master a couple times before your pull request can be merged.
What does Kumade do?
Before deploying, Kumade ensures the git repo is clean.
After that, it packages assets using
More, commits them, and pushes to origin.
Then it force pushes to the correct Heroku remote and runs
rake db:migrate on the
If any step fails, it immediately prints an error and stops the deploy process.
In your Gemfile:
kumade will deploy to any Heroku remote in the repo. For example, if you have a remote named "staging":
$ bundle exec kumade staging
To run in pretend mode, which prints what would be done without actually doing any of it:
$ bundle exec kumade staging -p
The default is to deploy to staging:
# equivalent to "bundle exec kumade staging" $ bundle exec kumade
Kumade auto-generates a deploy:ENV task for every Heroku environment.
# in your Rakefile: require 'kumade' $ rake deploy:staging
If you use rake tasks, you can't pass in options (like -p/--pretend).
Does it support the Cedar stack?
Yes. Kumade will automatically detect if your app is running on Cedar.
- MRI 1.8.7
- MRI 1.9.2
- REE 1.8.7
Want to run a task before bundling your assets on deploy? In your Rails app's rake tasks, drop in:
namespace :kumade do task :before_asset_compilation do puts "This runs before assets are committed and pushed to the remote" end end
You can hook in any custom code you want to run there before deploying!
What's with the name?
Kumade (pronunciation here) means "bamboo rake" in Japanese.
kumade is Copyright © thoughtbot. It is free software, and may be redistributed under the terms specified in the LICENSE file.