Add application.local.yml support

[ppworks]

Add "application.local.yml" support like a 'rails_config'

[laserlemon]

What value does this add?

[ppworks]

If you have OAuth credential in ENV like ENV['FB_APP_SECRET']
you can push 'config/application.yml' to public remote repository.
But can put your real credential into local disc and produciton server.

• config/application.yml for public

FB_APP_SECRET: 'dumy credential'

• config/application.local.yml for local or production

FB_APP_SECRET: 'your real credential'

and add .gitignore

config/application.local.yml

[laserlemon]

I see. The usefulness you're describing for application.local.yml is actually Figaro's intention for application.yml. Figaro's generator automatically Git-ignores application.yml for this reason. My workflow has been to commit an application.example.yml to my repository containing dummy values and comments as to which values are applicable to application.yml.

In an effort to simplify configuration management to the one application.yml file, I'm going to close the issue. But please feel free to continue the discussion here.

[coveralls]

Coverage remained the same when pulling 5d60346 on ppworks:merge_local_yaml into 61a4bd3 on laserlemon:master.

[Sinetheta]

The problem with application.example.yml is that your local setup then quickly falls out of date. I imagine we all add some form of the following to our bin/setup

  unless File.exist?("config/application.yml")
    system "cp config/application.yml.example config/application.yml"
  end

Which is great for a first install, but then you have to manually pull in changes from the example config forever forwards.

Alternatively, we could ignore application.local.yml and encourage people to check in application.yml as their "default values". No project setup required, the onus is now on environments which want to add overrides.