I found this article helpful as a starting point: (http://suitmymind.com/blog/2009/06/02/deploying-multiple-environments-on-heroku-while-still-hosting-code-on-github/ )
However, what we have done is the reverse of what the article suggests. Our staging environment is pointed at the default heroku reference (git heroku push, heroku db:push, etc.). Then we have a separate branch where our prod code is. So, to push to prod we need to do git heroku-prod production:master. Other commands are then heroku db:push --app our-app-name, etc. While it's certainly not failsafe it does make it less likely that you'll screw up something accidentally. Kelly Heikkila :coderow On Sep 11, 2009, at 6:03 AM, Neil wrote: > > I'm not sure if someone has already covered this, but although there > are loads of really handy features in the Heroku gem, some of the > functions that you can acheive are potentially very damaging to a > production environment and also very easy to do. > > For instance, from what I've seen there is nothing to stop me from > doing a db:push to my live application - there's no sort of question > of confirmation etc. > > Is this something that's planned or is it something I've just not > seen? > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
