Rails: Where to put configuration variables

Question

My team is maintaining a Rails application. The previous developer(s) decided to put some configuration variables (like facebook app id, twitter app id) as env variables. But this is not very versatile. If we have two applications (test and production), we are forced to use only one hardcoded configuration (or changing it manually). Also it is good practice to put these variables in the version control.

Is that the right way to do that? If not, what is the right way?

What do you mean, "hardcoded"? If you put them in code, then they will be hardcoded. Env vars are the way to go. — Sergio Tulentsev
– Sergio Tulentsev, Commented Feb 11, 2013 at 13:32

Bob · Accepted Answer · 2013-02-11 13:36:31Z

1

We are using following solution in 2 apps.

Store config variables in yml files for https://github.com/railsjedi/rails_config gem.
Apps are configured to use different yml files in production and dev modes via initializers.
On production servers directory with yml files are symlinked with 2 apps.

Task for capistrano looks so:

namespace :settings do
  task :symlink, roles: :app do
    run "ln -s /path_to_settings/#{rail_env} #{current_path}/config/settings"
  end
end

after "deploy:create_symlink", "settings:symlink"

answered Feb 11, 2013 at 13:36

Bob

2,12118 silver badges25 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Rails: Where to put configuration variables

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related