On Fri, Mar 20, 2009 at 7:58 AM, Mat Schaffer <[email protected]>wrote:
> another option would be to keep a heroku branch separate from your main > development branch and push from that rather than master. This branch > would have the config.yml in it w/ the password. Then deployment would > be: > > git checkout heroku > git merge master > git push heroku > This is a good technique, a number of folks are using this. One thing to remember is that the branch needs to be master on heroku. So you may need to do this on the final step: git push heroku heroku:master It might be a little clearer if you call the branch "deploy" or "production" or something like that, to avoid confusion with the remote name. Then it would be: git checkout deploy git merge master git push heroku deploy:master Adam --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
