Thanks guys. I guess it was an old topic, with these two links recycled from earlier posts:
http://jqr.github.com/2009/04/25/deploying-multiple-environments-on-heroku.html http://suitmymind.com/blog/2009/06/02/deploying-multiple-environments-on-heroku-while-still-hosting-code-on-github/ I would have identical environments down to the RACK_ENV=production for both. Rake is the way to go. Thanks for the gist. I would still deploy from a branch instead of a tag. Here is an example: $ git push staging deploy:master $ git push production deploy:master Tagging only after production has tested ok too. Also, I like http://semver.org/ better than tagging with dates. Versions incremented, possibly with http://github.com/dazuma/versionomy -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
