It works just fine - I use staging and production on Heroku (one Heroku app for each), and development locally. I use the herogit plugin to manage the different apps/repositories.
I'm not sure if you were implying as much, but I wouldn't recommend running a Heroku app in development - reserve that for your local environment. If you want a third app for "development", I'd recommend calling it something else (perhaps "unstable"). Also keep in mind also that you don't need to actually run them in different Rails environments - they can all use production, and you can change the settings you listed by setting environment variables (heroku config:add AWS_ACCESS_KEY_ID=1234567). That way you can keep your credentials out of your repository. --wuputah On Mon, May 3, 2010 at 1:31 PM, mtin79 <[email protected]> wrote: > hey out there, > i wanted to set up three specific environments with their own > variables (amazon s3, google map keys, ...) with custom names: > - development > - staging > - production > > i read that heroku only runs in production by default, but can be > customized with config vars to use a different environment namespace. > what are the ups and downs (or pitfalls) letting an heroku app run in > a custom rails environment? > > thanks for help! > > martin > > -- > 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]<heroku%[email protected]> > . > 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 [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.
