Sign in through GitHub

Please read for an updated status on RailsCasts:

Learn more or hide this

Chris Johnson's Profile

GitHub User: kindkid

Comments by Chris Johnson

Avatar

I do something similar. You may find the constantinople gem useful.

  1. Put all your non-secret config settings (eg - hostname), as well as "dummy" secrets into a config/app.yml.default file that you store in source control.

  2. Gitignore config/app.yml.

  3. In production, use chef templates to generate config/app.yml. Devs can also maintain their own local over-rides there as well.

If you prefer, instead of keeping config/app.yml.default and overriding with gitignore'd config/app.yml... you can keep config/app.yml in source control, and override with a gitignore'd config/app.yml.override