Deploying app ENV variables with Rbenv, Passenger and Capistrano(blog.intercityup.com)
blog.intercityup.com
Deploying app ENV variables with Rbenv, Passenger and Capistrano
http://blog.intercityup.com/deploying-app-env-variables-with-rbenv-passenger-and-capistrano/
2 comments
I'm going to go ahead and say that most people don't need rvm/rbenv/chruby etc in production.
Ask yourself if you really need multiple versions of ruby in production because if not you can save yourself the headache of setting it up.
Ask yourself if you really need multiple versions of ruby in production because if not you can save yourself the headache of setting it up.
We use it because we'd like to run multiple apps on one server. This way we can do that. With the added benefit of the .rbenv-vars to specify ENV.
Some other ideas that I've heard that may be better: store the secrets on a separate "offline" server that only the web server can talk to. Or have the file readable only by root, run a bootstrap script as root that would read the file, drop root privs, and then start the webserver.