jqr / heroku_san Goto Github PK

View Code? Open in Web Editor NEW

584.0 12.0 99.0 415 KB

Helpful stuffs for Heroku.

License: MIT License

Ruby 87.75% Gherkin 12.14% Shell 0.11%

heroku heroku-apps cli rake

heroku_san's People

Contributors

Stargazers

Watchers

Forkers

glennr iamnader epictetus lsemel pivotalexperimental brenthargrave leshill mrhaddad bryan-ash wink neutronz daveyeu bjhess mashion picuous davidmohara railsagile jcoene rahearn ryanwood notch8 esminc andyhite mdub matschaffer craigmarksmith copyhacker adamsiemion jemmyw johnbeynon azzab kyan pivotalforks joemsak mileszs kfitzpatrick spraints bendyworks niedfelj chargify maxwell hemang jberlinsky gaaady swrobel freundchen zawaideh ancamp pivotalzergling lacco blazingpair affluence-connect marcgg robotarmy albertpeng socialchorus topagentnetwork acanyon lastobelus vfiles rangerscience jphenow banyan danielgrippi slothbear turlockmike danielwright xinminlabs lyahdav tjgrathwell justin808 kjs3 vtorves ashanbrown homelight manish211 nicolasleger zephyr-dev randypray mackmakudo cureus kmayer thinknear ichiroc viewthespace tansaku bearerpipelinetest forky-mcforkface sljh0214 iq-scm cesar-flores-tx

heroku_san's Issues

Outreach

Hey guys. Sorry to file this as an issue (since it isn't really one), but this seemed like the clearest way to contact you all. I currently maintain the heroku gem and find what you are doing here pretty interesting. From that I have a couple points.

You may want to consider using http://github.com/heroku/heroku.rb instead of the heroku client from heroku/heroku. It has built in mocking, better consistency and some other niceties that might make your lives a bit easier. Plus I would love to have more people using it and helping to make it better (I hope to port the CLI to using it in the not too distant future and deprecate/remove the existing client).
My door is always open. It is clear that you guys have spent some time considering how to make some use cases much easier to deal with and knowing more about this kind of stuff is super valuable for me. So if you have any questions or suggestions about how we can change the CLI, client, API, etc to make things easier I am all ears. Plus if you just need help on integrating or otherwise, like I said, feel free to ping me so that I can help out.

Thanks for your awesome work!

rake environment db:rollback does not do what you expect

Seems to just run db:rollback in the dev environment...

Multiple Executions?

When I use heroku_san I get the following output:

heli:myapp heli$ rake staging heroku:maintenance
(in /Users/heli/hemju/programming/workspace/rubymine/myapp)
heroku maintenance:on --app myapp-staging
Maintenance mode enabled.
heroku maintenance:on --app myapp-staging
Maintenance mode enabled.

heroku maintenance:on --app myapp-staging
Maintenance mode enabled.
heroku maintenance:on --app myapp-staging
Maintenance mode enabled.

Using heroku directly:

heli:myapp heli$ heroku maintenance:on --app myapp-staging
Maintenance mode enabled.
heli:myapp heli$

Add callbacks support

Hello,

It'd be super cool if we'd be able to add some callbacks to the deployment.
For exemple, I'm using the GitHub Javascript Strategy to bundle my JS and CSS. And I'd really like to do it automatically every time I deploy.

heroku_san support for Sinatra?

Any thoughts on supporting Sinatra-based projects?

A user can add a warning/delay for certain environments/actions

rake [stage] shell

Heroku run bash --app ...

remotes don't show up in git list

I just recently started using this, and I've noticed that though I can rake staging deploy or rake production deploy (so I know those two remotes are set up properly), when I git branch -a I get this:

$ git br -a
* autocomplete_plugin
  master
  redesign
  remotes/heroku/master

Why don't the remotes created with rake all heroku:remotes show up? Why does my old remote still show up, though I won't be using it anymore?

Add support for multi process tasks

Add tasks https://github.com/camelmasa/heroku_san

rake heroku:parallel:create # Creates the Heroku app (multi prosess)
rake heroku:parallel:remove # Removes the Heroku app (multi prosess)
rake heroku:parallel:config # Add config:vars to each application. (multi prosess)
rake heroku:parallel:restart # Restarts remote servers (multi prosess)
rake heroku:parallel:maintenance # Enable maintenance mode (multi prosess)
rake heroku:parallel:maintenance_off # Disable maintenance mode (multi prosess)
rake heroku:parallel:maintenance_on # Enable maintenance mode (multi prosess)
rake heroku:parallel:push[commit] # Pushes the given commit (default: HEAD) (multi prosess)
rake heroku:parallel:push:force[commit] # Force-pushes the given commit (default: HEAD) (multi prosess)

Should not restart if migrate does nothing

Handle "Stacks"

Could you add 'ps' tasks ?

It would be helpful for things like watch heroku ps --app my-app-among-others !
Anyway, great gem =)

Yann

Error with Procfile

I tried to use heroku_san for 3 environments: working, staging and production.
In production it contains Procfile (for scaling etc), and the Procfile should not used in working and staging environments.
I got this error:

"Heroku push rejected, Procfile is not supported on the Bamboo stack"

What is workaround to fix this error? CMIIW

Thanks,
Dimas

Ignore configs with a blank app name

A couple of things happening here:

% rake staging heroku:create heroku:rack_env
...create succeeds...
heroku config --app
heroku config:add --app RACK_ENV=development
Usage: heroku config:add = [= ...]
rake aborted!
Command failed with status (1): [heroku config:add --app RACK_ENV=developm...]

The staging task has been somehow ignored for heroku:rack_env
The app for development is not set (config file below):

development:
app:
config:
STUFF: STUFF

No such file to load -- rails, Rails v2.3.8

I recently deleted all my gems in the gemset I was using and reran bundler to build up only the gems I needed for my project, and now when I include heroku_san in my Gemfile, I get the following error every time I run rake.

Do you have any idea why heroku_san is raising this error?

I am using heroku_san 1.0.1 and Rails 2.3.8

ERROR:
rake aborted!
no such file to load -- rails
/Users/matthew/.rvm/gems/ruby-1.8.7-p302/gems/activesupport-2.3.8/lib/active_support/dependencies.rb:156:in require' /Users/matthew/.rvm/gems/ruby-1.8.7-p302/gems/activesupport-2.3.8/lib/active_support/dependencies.rb:156:inrequire'
/Users/matthew/.rvm/gems/ruby-1.8.7-p302/gems/activesupport-2.3.8/lib/active_support/dependencies.rb:521:in new_constants_in' /Users/matthew/.rvm/gems/ruby-1.8.7-p302/gems/activesupport-2.3.8/lib/active_support/dependencies.rb:156:inrequire'
/Users/matthew/.rvm/gems/ruby-1.8.7-p302/gems/heroku_san-1.0.1/lib/heroku_san/railtie.rb:1
/Users/matthew/.rvm/gems/ruby-1.8.7-p302/gems/activesupport-2.3.8/lib/active_support/dependencies.rb:156:in require' /Users/matthew/.rvm/gems/ruby-1.8.7-p302/gems/activesupport-2.3.8/lib/active_support/dependencies.rb:156:inrequire'
/Users/matthew/.rvm/gems/ruby-1.8.7-p302/gems/activesupport-2.3.8/lib/active_support/dependencies.rb:521:in new_constants_in' /Users/matthew/.rvm/gems/ruby-1.8.7-p302/gems/activesupport-2.3.8/lib/active_support/dependencies.rb:156:inrequire'
/Users/matthew/.rvm/gems/ruby-1.8.7-p302/gems/heroku_san-1.0.1/lib/heroku_san.rb:1
/Users/matthew/.rvm/gems/ruby-1.8.7-p302/gems/bundler-1.0.0/lib/bundler/runtime.rb:64:in require' /Users/matthew/.rvm/gems/ruby-1.8.7-p302/gems/bundler-1.0.0/lib/bundler/runtime.rb:64:inrequire'
/Users/matthew/.rvm/gems/ruby-1.8.7-p302/gems/bundler-1.0.0/lib/bundler/runtime.rb:62:in each' /Users/matthew/.rvm/gems/ruby-1.8.7-p302/gems/bundler-1.0.0/lib/bundler/runtime.rb:62:inrequire'
/Users/matthew/.rvm/gems/ruby-1.8.7-p302/gems/bundler-1.0.0/lib/bundler/runtime.rb:51:in each' /Users/matthew/.rvm/gems/ruby-1.8.7-p302/gems/bundler-1.0.0/lib/bundler/runtime.rb:51:inrequire'
/Users/matthew/.rvm/gems/ruby-1.8.7-p302/gems/bundler-1.0.0/lib/bundler.rb:112:in require' /Users/matthew/Projects/brc/brc/config/boot.rb:115:inload_gems'

implement the equivalent of heroku config --long

How can I get the same via heroku-san?

Requires old version of heroku gem

Slightly confused. I've looked through all the source here and can't find a reason that heroku_san would require the heroku gem version 1.6.3 but running bundle install fails now because I have another gem that requires heroku gem >= 1.13.7

This probably has something to do with the fact that some of the heroku san commands (for example rake staging logs doesn't work anymore either.

Distribute as a gem?

This could be useful for an Rack app. Thought about releasing as a gem rather than just a plugin?

What is the proper syntax for db:push and pull?

Hello, loving the functionality, but I can't seem to get the push and pull tasks to work..

I've tried "rake db:push" as per the readme and get

** Invoke db:push (first_time)
** Execute db:push
rake aborted!

I've also tried "rake staging db:push" and got

** Invoke staging (first_time)
** Execute staging
** Invoke db:push (first_time)
** Execute db:push
rake aborted!

Any help would be great, thanks!

rake 'env' heroku:share runs twice

$ rake staging heroku:share
(in /Users/joe/Projects/.../...)
Email address of collaborator to add: [entered email]
heroku sharing:add --app [app-name] [entered email]
[entered email] added as a collaborator on [app-name].
heroku sharing:add --app [app-name] [entered email]
User user is already a collaborator on the app

heroku_san generating warnings on Rake 0.9.2

When running rake, Rake complains that heroku_san is using a deprecated access strategy:

WARNING: Global access to Rake DSL methods is deprecated.  Please include
    ...  Rake::DSL into classes and modules which use the Rake DSL methods.
WARNING: DSL method MyApplication::Application#task called at /home/foouser/.rvm/gems/ruby-1.9.2-p180@cardagin-web/gems/railties-3.0.7/lib/rails/application.rb:215:in `initialize_tasks'
WARNING: 'task :t, arg, :needs => [deps]' is deprecated.  Please use 'task :t, [args] => [deps]' instead.
    at /home/foouser/.rvm/gems/ruby-1.9.2-p180@cardagin-web/bundler/gems/heroku_san-19d603ee32a6/lib/heroku_san/tasks.rb:229:in `<top (required)>'

Command failed on creating config.yml, but config.yml is created

I know I'm issue crazy, sorry guys but I just keep getting errors

$ rake heroku:create_config
(in /Users/.../.../...)
Copied example config to config/heroku.yml
/Users/joe/.../.../config/heroku.yml
rake aborted!
Command failed with status (127): [ /Users/joe/.../.../config/heroku.y...]

But it is there and works fine...

Basically it appears that every command I run tries to run twice.

Remove Rails dependency

I don't think we need to require rails. It is supported with rail ties, but not required. We can support Sinatra apps!

Unable to seed a new app

Hey, is there a command for seeding a new app? Thanks.

Replace shell commands to heroku command line with gem API calls

Note to self, use the heroku gem's API instead of shelling out. It should make it easier to test (stub out Heroku calls instead of inferring via sh calls), better guarantee that the interface is "right". The spec files in the heroku gem look pretty complete, so it should not be difficult to switch. We might have some issues around authentication. Need to experiment a little.

cf: https://github.com/heroku/heroku

heroku_san stalling at migration step

I'm not 100% sure if this is a heroku_san problem, but my deployments are getting stuck at the migration step. If I run the heroku migration command it works fine (heroku rake --app appname db:migrate), but when run via heroku_san it stalls.

Any suggestions?

A developer can synchronize Heroku ENV variables

It would be nice if we could control Heroku ENV variables from within the configuration yaml file. Easy to add a new host or update.

Deploying to Heroku's Cedar stack blows up because of wrong db:migrate format

A deployment to Cedar causes the deployment to fail:

heroku rake --app some-app db:migrate
 !   For Cedar apps, use: `heroku run rake db:migrate`
rake aborted!
Command failed with status (1): [heroku rake --app some-app db:migrate]

configurable db:migrate or restart

Issue with rake heroku:create_config command

I get the following error after installing the latest gem.

macbook-pro:cvmongo Ben$ sudo rake heroku:create_config --trace
(in /Users/Ben/Dropbox/Web/cvmongo)
** Invoke heroku:create_config (first_time)
** Execute heroku:create_config
Copied example config to config/heroku.yml
/Users/Ben/Dropbox/Web/cvmongo/config/heroku.yml
rake aborted!
Command failed with status (127): [ /Users/Ben/Dropbox/Web/cvmongo/config/her...]
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:995:in sh' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:1010:incall'
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:1010:in sh' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:1094:insh'
/Library/Ruby/Gems/1.8/gems/heroku_san-1.0.8/lib/heroku_san/tasks.rb:111
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in call' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:inexecute'
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in each' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:inexecute'
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in invoke_with_call_chain' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/monitor.rb:242:insynchronize'
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in invoke_with_call_chain' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:ininvoke'
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in invoke_task' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:intop_level'
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in each' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:intop_level'
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in standard_exception_handling' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:intop_level'
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in run' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:instandard_exception_handling'
/Library/Ruby/Gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in run' /Library/Ruby/Gems/1.8/gems/rake-0.8.7/bin/rake:31 /usr/bin/rake:19:inload'
/usr/bin/rake:19
macbook-pro:cvmongo

Error with rake <X> deploy:force

It seems that based on the parameters given I should not need to give a commit, but it seems like deploy:force does not work. I'm using ZSH on OS X, if that assists in debugging the problem at all.

    project> rake -T deploy 
    (in ~/Documents/dev/project)
    rake after_deploy          # Callback after deploys
    rake before_deploy         # Callback before deploys
    rake deploy[commit]        # Pushes the given commit, migrates and restarts (default: HEAD)
    rake deploy:force[commit]  # Force-pushes the given commit, migrates and restarts (default: HEAD)
    rake hoptoad:deploy        # Notify Hoptoad of a new deploy.

    project> rake demo deploy:force --trace
    (in ~/Documents/dev/project)
    WARNING: Nokogiri was built against LibXML version 2.7.7, but has dynamically loaded 2.7.3
    ** Invoke demo (first_time)
    ** Execute demo
    ** Invoke deploy:force (first_time)
    ** Execute deploy:force
    ** Invoke deploy (first_time)
    ** Invoke before_deploy (first_time)
    ** Execute before_deploy
    ** Execute deploy
    git update-ref refs/heroku_san/deploy {}
    fatal: {}: not a valid SHA1
    git update-ref -d refs/heroku_san/deploy
    rake aborted!
    Command failed with status (128): [git update-ref refs/heroku_san/deploy {}...]
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:995:in `block in sh'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:1010:in `call'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:1010:in `sh'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:1094:in `sh'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/heroku_san-1.0.6/lib/heroku_san/tasks.rb:257:in `push'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/heroku_san-1.0.6/lib/heroku_san/tasks.rb:149:in `block (2 levels) in <top (required)>'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/heroku_san-1.0.6/lib/heroku_san/tasks.rb:237:in `block in each_heroku_app'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/heroku_san-1.0.6/lib/heroku_san/tasks.rb:235:in `each'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/heroku_san-1.0.6/lib/heroku_san/tasks.rb:235:in `each_heroku_app'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/heroku_san-1.0.6/lib/heroku_san/tasks.rb:148:in `block in <top (required)>'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:636:in `call'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:636:in `block in execute'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:631:in `each'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:631:in `execute'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:597:in `block in invoke_with_call_chain'
    ~/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:583:in `invoke'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/heroku_san-1.0.6/lib/heroku_san/tasks.rb:160:in `block (2 levels) in <top (required)>'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:636:in `call'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:636:in `block in execute'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:631:in `each'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:631:in `execute'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:597:in `block in invoke_with_call_chain'
    ~/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:583:in `invoke'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:2029:in `block (2 levels) in top_level'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:2029:in `each'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:2029:in `block in top_level'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:2001:in `block in run'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/gems/rake-0.8.7/bin/rake:31:in `<top (required)>'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/bin/rake:19:in `load'
    ~/.rvm/gems/ruby-1.9.2-p0@gemset/bin/rake:19:in `<main>'

sharing:transfer support

Support Heroku bundles

I find myself doing a lot of bundle commands all of the sudden, uhg!

rake 'env' logs gives unsupported client error

$ rake staging logs
(in /Users/.../.../...)
heroku logs --app [app-name]
This feature is not supported by your client version.

However:
heroku logs --app [app-name]
results in the logs

rake logs ... make it tail by default?

A couple reasons I'd like it to tail:

rake takes forever to load the env, so resulting in just one page of output; re-running rake logs again means I have to wait.
generally when I'm tailing, I am looking at an error on my staging app so I want to keep the log tail-ing.

Would you be open to accepting a pull request to make the default behavior of rake logs to tail instead of just producing one page of output?

rake production deploy running 4 times

So this is a strange one. It just started happening yesterday on one of my apps running Rails 3.0.6 and Ruby 1.9.2. When I run rake production deploy the proper sequence for deploying runs 4 full times. Obviously updating code and relaunching the updated app on heroku the first time but then just 3 more times saying "Everything up-to-date".

Anyone else seeing behavior like this? Clearly this issue isn't too high priority because deploys are still working but it's a little strange.

Rails 3.0.6 & Rails 3.0.7.rc1
Ruby 1.9.2
heroku gem 1.20.1
heroku_san gem 1.1.0
I have a before_deploy rake task as well that does a little extra processing before the actual deploy takes place. This happens on the first lap through deploy process but not the subsequent 3.

refspec issue

┌─[tim@tim-macbookpro] - [~/code/ervscafe] - [git:master]
└─[$]>➜ rake production deploy
(in /Users/tim/code/ervscafe)
git push [email protected]:ervs-cafe-production.git master:master && heroku rake --app ervs-cafe-production db:migrate && heroku restart --app ervs-cafe-production
error: src refspec master does not match any.
error: failed to push some refs to '[email protected]:ervs-cafe-production.git'

When attempting to deploy, the above error appears. If I cp the command and paste it, works fine. Immediately after, try the heroku_san deploy again, same error.

deploy task no longer outputs that it restarted app

I swear heroku_san used to output something to indicate that my app was restarted after the migration step of a deploy completed. Now it just dumps back to the shell after the migration, and while the app seems to restart, it doesn't give me any indication that it did.

I was using heroku_san 2.1.0 w/ heroku gem 2.21.3 before and now I'm on 2.1.3 & 2.23.0 (latest as of this writing). Could be a heroku or heroku_san issue I suppose...

Automatically add a reasonable slugignore

Task for verifying addons are the same across all apps

rake all heroku:config - "undefined local variable"

Running "rake all heroku:config" with the "pivotal-merge" branch, I get the output:

rake aborted!
undefined local variable or method config' for main:Object [REDACTED]/bundler/gems/heroku_san-0c5fa6b080d0/lib/tasks.rb:102:inblock (3 levels) in <top (required)>'

Gemfile:

gem "heroku_san", :git => "git://github.com/fastestforward/heroku_san.git", :branch => 'pivotal-merge'

Add a force deploy task

Should support non-master branch deploys

rake {stage} deploy:force fails

bliss:sumuru (master) km bt$ rake --trace acceptance deploy:force
** Invoke acceptance (first_time)
** Invoke heroku:stage:acceptance (first_time)
** Execute heroku:stage:acceptance
** Execute acceptance
** Invoke deploy:force (first_time)
** Invoke heroku:deploy:force (first_time)
** Invoke before_deploy (first_time)
** Invoke heroku:deploy:before (first_time)
** Execute heroku:deploy:before
** Execute before_deploy
** Execute heroku:deploy:force
rake aborted!
undefined method `[]' for nil:NilClass
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/heroku_san-3.0.0/lib/heroku_san/deploy/base.rb:10:in `deploy'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/heroku_san-3.0.0/lib/heroku_san/deploy/rails.rb:7:in `deploy'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/heroku_san-3.0.0/lib/heroku_san/stage.rb:70:in `deploy'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/heroku_san-3.0.0/lib/heroku_san/tasks.rb:222:in `block (4 levels) in <top (required)>'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/heroku_san-3.0.0/lib/heroku_san/project.rb:65:in `block in each_app'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/heroku_san-3.0.0/lib/heroku_san/project.rb:64:in `each'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/heroku_san-3.0.0/lib/heroku_san/project.rb:64:in `each_app'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/heroku_san-3.0.0/lib/heroku_san/tasks.rb:333:in `each_heroku_app'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/heroku_san-3.0.0/lib/heroku_san/tasks.rb:221:in `block (3 levels) in <top (required)>'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/task.rb:205:in `call'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/task.rb:205:in `block in execute'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/task.rb:200:in `each'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/task.rb:200:in `execute'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/task.rb:158:in `block in invoke_with_call_chain'
/Users/pivotal/.rvm/rubies/ruby-1.9.3-p194-perf/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/task.rb:151:in `invoke_with_call_chain'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/task.rb:176:in `block in invoke_prerequisites'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/task.rb:174:in `each'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/task.rb:174:in `invoke_prerequisites'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/task.rb:157:in `block in invoke_with_call_chain'
/Users/pivotal/.rvm/rubies/ruby-1.9.3-p194-perf/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/task.rb:151:in `invoke_with_call_chain'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/task.rb:144:in `invoke'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/application.rb:116:in `invoke_task'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `block (2 levels) in top_level'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `each'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `block in top_level'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/application.rb:88:in `top_level'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/application.rb:66:in `block in run'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/lib/rake/application.rb:63:in `run'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/gems/rake-0.9.2.2/bin/rake:33:in `<top (required)>'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/bin/rake:23:in `load'
/Users/pivotal/.rvm/gems/ruby-1.9.3-p194-perf@sumuru/bin/rake:23:in `<main>'
Tasks: TOP => deploy:force => heroku:deploy:force

DB pull/push API changed?

Wonderful gem, keep up the good work! One issue however is that I can't seem to get the DB pull/push working. When run, Heroku responds saying the command isn't found. Is it possible that the API for Heroku has changed? Details are below. Any help would be greatly appreciated! Thanks :-)

Note: I replaced my app name with [my-app] as this is a sensitive project at the moment. Thanks again.

rake production heroku:db:pull
heroku pgdumps:capture --app [my-app]
! pgdumps:capture is not a heroku command.
! See heroku help for additional details.
rake aborted!
Command failed with status (1): [heroku pgdumps:capture --app [my-app]...]

tasks.rb:112: syntax error, unexpected ':', expecting kEND

/Library/Ruby/Gems/1.8/gems/heroku_san-2.1.1/lib/tasks.rb:112: syntax error, unexpected ':', expecting kEND
puts stage.push_config RACK_ENV: stage.name

Update README.rdoc for v2

The good news is that there are lots of cool new features and bug fixes.

The bad news is that the READ is out of date.

Separate file for sensitive config vars

I'd love to keep config/heroku.yml with the git repository, but that precludes it from containing API keys and passwords. Any chance there could be a separate file (say, heroku-sensitive.yml) that contains sensitive information and is thus much easier to .gitignore?

Thanks!

500 error when running `rake all heroku:create heroku:rack_env`

I'm getting a 500 error when running the above mentioned command. This seems to be a new issue within the last 48 hours as I just deployed another app with no issues. Using Ruby 1.9.3p0 and Rails 3.2.2

Config:

production: 
  app: cofeeapp
  stack: cedar
  config:
    BUNDLE_WITHOUT: "development:test"

staging:
  stack: cedar
  app: cofeeapp-staging
  config: &default
    BUNDLE_WITHOUT: "development:test"

Gem versions:

heroku (2.23.0)
heroku_san (2.1.1)

Output:

$ rake all heroku:create heroku:rack_env --trace
** Invoke all (first_time)
** Invoke heroku:stage:all (first_time)
** Execute heroku:stage:all
** Execute all
** Invoke heroku:create (first_time)
** Execute heroku:create
production: Created cofeeapp
staging: Created cofeeapp-staging

** Invoke heroku:rack_env (first_time)
** Invoke heroku:config:rack_env (first_time)
** Invoke all 
** Execute heroku:config:rack_env
heroku config --app cofeeapp
rake aborted!
500 Internal Server Error
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rest-client-1.6.7/lib/restclient/abstract_response.rb:48:in `return!'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rest-client-1.6.7/lib/restclient/request.rb:230:in `process_result'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rest-client-1.6.7/lib/restclient/request.rb:178:in `block in transmit'
/Users/kyle/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/net/http.rb:745:in `start'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rest-client-1.6.7/lib/restclient/request.rb:172:in `transmit'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rest-client-1.6.7/lib/restclient/request.rb:64:in `execute'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rest-client-1.6.7/lib/restclient/request.rb:33:in `execute'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rest-client-1.6.7/lib/restclient/resource.rb:76:in `put'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/heroku-2.23.0/lib/heroku/client.rb:601:in `process'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/heroku-2.23.0/lib/heroku/client.rb:587:in `put'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/heroku-2.23.0/lib/heroku/client.rb:465:in `add_config_vars'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/heroku_san-2.1.1/lib/heroku_san/stage.rb:96:in `push_config'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/heroku_san-2.1.1/lib/tasks.rb:112:in `block (4 levels) in <top (required)>'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/heroku_san-2.1.1/lib/heroku_san/project.rb:62:in `block in each_app'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/heroku_san-2.1.1/lib/heroku_san/project.rb:61:in `each'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/heroku_san-2.1.1/lib/heroku_san/project.rb:61:in `each_app'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/heroku_san-2.1.1/lib/tasks.rb:300:in `each_heroku_app'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/heroku_san-2.1.1/lib/tasks.rb:107:in `block (3 levels) in <top (required)>'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/task.rb:205:in `call'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/task.rb:205:in `block in execute'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/task.rb:200:in `each'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/task.rb:200:in `execute'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/task.rb:158:in `block in invoke_with_call_chain'
/Users/kyle/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/task.rb:151:in `invoke_with_call_chain'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/task.rb:176:in `block in invoke_prerequisites'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/task.rb:174:in `each'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/task.rb:174:in `invoke_prerequisites'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/task.rb:157:in `block in invoke_with_call_chain'
/Users/kyle/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/task.rb:151:in `invoke_with_call_chain'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/task.rb:144:in `invoke'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/application.rb:116:in `invoke_task'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `block (2 levels) in top_level'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `each'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `block in top_level'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/application.rb:88:in `top_level'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/application.rb:66:in `block in run'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/lib/rake/application.rb:63:in `run'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/gems/rake-0.9.2.2/bin/rake:33:in `<top (required)>'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/bin/rake:19:in `load'
/Users/kyle/.rvm/gems/ruby-1.9.3-p0@cofee2/bin/rake:19:in `<main>'
Tasks: TOP => heroku:rack_env => heroku:config:rack_env

rake demo deploy[commit] doesn't respect tag

rake demo heroku:deploy[commit] works just find, but it would be great if rake demo deploy[commit] worked as well. Currently, it just ignores the commit and defaults silently to HEAD.