Rails initializer for development and production

Question

I have the following code in /config/initializers/chargify.rb

Chargify.configure do |c|
  c.subdomain = 'example'
  c.api_key   = '123xyz'
end

But I have different settings for development and production.

So, how would I have a different set of variables values based on environment?

Josh, is this what went into Baremetrics' MVP? History in the making right here :) — Jan Klimo, Jun 06 '18 at 07:28
@JanKlimo Haha, naaa. This was over 3 years before Baremetrics was even an idea in my brain. :P — Shpigford, Jun 06 '18 at 14:44

score 29 · Accepted Answer · edited Feb 22 '15 at 19:17

29

I would create a config file for this (config/chargify.yml):

development:
  subdomain: example
  api_key: 123abc
production:
  subdomain: production_domain
  api_key: 890xyz

And then change your Initializer like this:

chargify_config_file = File.join(Rails.root,'config','chargify.yml')
raise "#{chargify_config_file} is missing!" unless File.exists? chargify_config_file
chargify_config = YAML.load_file(chargify_config_file)[Rails.env].symbolize_keys

Chargify.configure do |c|
  c.subdomain = chargify_config[:subdomain]
  c.api_key   = chargify_config[:api_key]
end

edited Feb 22 '15 at 19:17

Freedom_Ben

11,247
10
69
89

answered May 12 '10 at 13:17

jigfox

18,057
3
60
73

1

Quick warning for anyone cutting and pasting from above: `sudomain: example` should be `subdomain: example` – Jules Copeland May 22 '12 at 10:03

score 5 · Answer 2 · edited Dec 31 '13 at 06:30

What about:

Chargify.configure do |c|
  if Rails.env.production?
    # production settings
    c.api_key   = '123xyz'
  else
    # dev. and test settings
    c.api_key   = '123xyz'
  end
end

Better yet, you can reduce duplication with case block:

Chargify.configure do |c|
  c.subdomain = 'example'
  c.api_key   = case
    when Rails.env.production?
      '123xyz'
    when Rails.env.staging?
      'abc123'
    else
      'xyz123'
    end
end

score 4 · Answer 3 · answered May 12 '10 at 13:14

4

If you're going to need different settings for different environments, it's best to put them in the respective environment file, like config/environments/development.rb.

If you absolutely insist on putting them in an initializer (but please don't, that's what the environment files are for), you can use a case statement and inspect the value of Rails.env, which returns the name of the current environment as a string.

answered May 12 '10 at 13:14

ryeguy

65,519
58
198
260

The comments in application.rb to *not* put configuration on those files and to put it in files in the initializers directory. – Stewart Johnson Jan 11 '12 at 23:07

score 1 · Answer 4 · answered May 04 '17 at 13:02

I would suggest you to use env variables

Chargify.configure do |c|
  c.subdomain = ENV['APP_SUBDOMAIN']
  c.api_key = ENV['API_KEY']
end

and set appropriate variables in ~/.bashrc or ~/.profile but note: this must be set for same user as Rails instance is opareting on. E.g. deploy user specified in capistrano is you used that for deployments

Rails initializer for development and production

4 Answers4