Re: heroku config:add BUNDLE_WITHOUT=development:test
A lot of my apps aren't production apps so I'm fairly glad this isn't the default behaviour Neil On 3 Dec 2010 00:41, Todd profes...@gmail.com wrote: I've been curious why heroku deploys my development and test gems onto my production machine. In the latest newsletter they mention adding the following line to prevent that from happening. My question is, why isn't this the default behavior? heroku config:add BUNDLE_WITHOUT=development:test From the newsletter. Specify gems to bundle in production Is your slug getting too big? Taking too long to compile? One of the most common reasons for that is a bloated Gemfile. There's no reason to include the gems from your development and test groups when you push to Heroku, so you can exclude them by setting a config var: $ heroku config:add BUNDLE_WITHOUT=development:test Once that's added, future deploys will automatically ignore gems in the development and test groups—or whatever other groups you want to exclude. -- 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 heroku%2bunsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- 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.
Re: github help
I've added a new remote origin, but what do I change the remote name to (does it matter) and the fetch line in my .git/config file? [remote heroku-staging] url = g...@heroku.com:myapp-staging.git fetch = +refs/heads/*:refs/remotes/heroku-staging/* [remote heroku-prod] url = g...@heroku.com:myapp.git fetch = +refs/heads/*:refs/remotes/heroku-prod/* At the moment I've added the lines above, but I'm a bit concerned that now I've changed things, when I run 'git push heroku-prod master' (assuming that's right!) it won't push a load of nonsense or break my live app. Or do I just have to try it! Cheers, Graeme On 2 December 2010 12:10, Alex a...@heaton.me wrote: Hopefully I haven't misunderstood. : Create a new repo on github, follow it's instructions for adding an existing project. (something like 'git remote add origin g...@github.com/blablabla' ) Now, just push and pull from your github repo instead. When you want to send changes to heroku, do a push to heroku. Use different branches for different release stages (staging, production etc). Does that make sense? On Dec 1, 1:59 pm, Graeme Simpson gra...@simmo.gs wrote: Hi there, I have an app on heroku at the moment and so far we've just been using git on heroku as our main repository. We need to switch things around so we use github most of the time and have a separate app for staging and testing. I found this excellent guide for setting up github with herokuhttp:// suitmymind.com/blog/2009/06/02/deploying-multiple-environments... but it only covers new applications. Does anyone have any instructions (or could point me at an alternative guide) for switch the repos around to use github as the master? Thanks, Graeme -- 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.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- 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.
Re: github help
You may want to double check the ref on prod. I see the app name is myapp but the ref is myapp-prod. (may be correct or a translation layer) Also, you may want to create a local branch for production. Up to you. Have that branch tied to production. But that is up to you / your workflow. Last: you have staging. If that is working for you, then it would seem prod should work as well. --K On Dec 3, 2010, at 5:47 AM, Graeme Simpson gra...@simmo.gs wrote: I've added a new remote origin, but what do I change the remote name to (does it matter) and the fetch line in my .git/config file? [remote heroku-staging] url = g...@heroku.com:myapp-staging.git fetch = +refs/heads/*:refs/remotes/heroku-staging/* [remote heroku-prod] url = g...@heroku.com:myapp.git fetch = +refs/heads/*:refs/remotes/heroku-prod/* At the moment I've added the lines above, but I'm a bit concerned that now I've changed things, when I run 'git push heroku-prod master' (assuming that's right!) it won't push a load of nonsense or break my live app. Or do I just have to try it! Cheers, Graeme On 2 December 2010 12:10, Alex a...@heaton.me wrote: Hopefully I haven't misunderstood. : Create a new repo on github, follow it's instructions for adding an existing project. (something like 'git remote add origin g...@github.com/blablabla' ) Now, just push and pull from your github repo instead. When you want to send changes to heroku, do a push to heroku. Use different branches for different release stages (staging, production etc). Does that make sense? On Dec 1, 1:59 pm, Graeme Simpson gra...@simmo.gs wrote: Hi there, I have an app on heroku at the moment and so far we've just been using git on heroku as our main repository. We need to switch things around so we use github most of the time and have a separate app for staging and testing. I found this excellent guide for setting up github with herokuhttp://suitmymind.com/blog/2009/06/02/deploying-multiple-environments... but it only covers new applications. Does anyone have any instructions (or could point me at an alternative guide) for switch the repos around to use github as the master? Thanks, Graeme -- 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. -- 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. -- 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.
