Multiple environments, non heroku

[prasann]

I have a total of 6 environments to be deployed. Currently all the passwords are there in a single application.yml file. I am deploying to my own app server using Capistrano. I have written a task to copy the application.yml file from local to the deploy box's shared directory and create a symlink to the shared directory from current.

This works well. Since these keys don't change often, i have commented out the file copy part so accidentally application.yml file is not overwritten.

Just wanted to check with the people how they manage the keys using Figaro, Capistrano combination.

Now one problem i see is that all my environments have all the keys and passwords. Any better way to do this?

[dmitrym0]

I thought

Figaro convention is to never commit configuration files.

but that doesn't answer your question (or mine). I'm in a similar boat.

[amitpatelx]

I too have similar requirement.

We have been using AWS and any settings store locally ends up being burnt into the machine image from which new instances are launched. So if any settings change, we'll have to burn a new machine image and relaunch whatever number is running.