Yeah, it would be awesome to see that out-of-the-box in Rails. -- LAILSON BANDEIRA http://lailson.me/
On Jan 14, 2013, at 6:26 PM, mateo <[email protected]> wrote: > Another option would be to add support for Procfile and/or .env files, either > via Foreman, or integrating function similar to the dotenv gem > (https://github.com/bkeepers/dotenv). The .env files offer a simple way to > handle environment variables, and the Procfile simplifes developing > applications that use queues and other background services. It also eases > deployment, not just to heroku but also other systems, via the `forman > export` command. > > On Sunday, January 13, 2013 4:59:49 PM UTC-5, Jay Feldblum wrote: > > Rails could even help this along, by natively supporting reading a > config/environment.yml file with environment variables. The file would be > gitignored by default and Capistrano could symlink in a production > config/environment.yml file when deploying. But it's easy to extend your own > application to try to read config/environment.yml early in the boot phase on > your own. > > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/rubyonrails-core/-/C4zE26uWQcoJ. > 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-core?hl=en. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en.
