David Kahn wrote in post #961052: > On Fri, Nov 12, 2010 at 11:45 AM, Marnen Laibow-Koser > <[email protected]>wrote: > >> >> >> If that's all, then it's probably not necessary. Heroku has its own >> configuration interface for setting environment variables (and you could >> set RAILS_ENV if you wanted it to be "production_heroku" instead of >> "production"). >> > > For one, my storage location is different - I use S3. This is probably > the > only major setting difference. Right now I manually change the variable, > but > that opens me up to not turning it off when I push to production.
No, in fact it doesn't. Heroku has a completely independent interface for setting config variables, so there's nothing to forget to turn off. See http://docs.heroku.com/config-vars. > So you > are > saying I could create a new rails environment that is Heroku? Do you > know > offhand how I would tell heroku to use "production_heroku" rather than > production? I thought it just automatically used "production" in all > cases. Rails always, always, always uses whatever environment RAILS_ENV tells it to use (or "development" if RAILS_ENV isn't set). So just set RAILS_ENV to something else. Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
