Skip to content

Conversation

@greghaygood
Copy link

I've updated SettingsLogic to support multiple files, in order to allow local environments to override settings in source control managed global files as needed.

@igor-alexandrov
Copy link

Here is Gist, how this can be easily done without any patching.
https://gist.github.com/1462080

@vitaliel
Copy link

Hello,

Thanks for the feature, but it will look better if we will have support for config directories:

/etc/app_name.d/
/etc/app_name.yml

and these directories can contain more *.yml files.

@enortham
Copy link

enortham commented Jan 8, 2013

I was thinking about doing the same because I have secure information that I want to be different in staging and production. Generally the file is going to be sym linked during a deploy. I realized that it was easier to just create another Settings Logic object for example SecureSettings and link/overwrite the development/test version of the config file. We don't store the sensitive information in source control so this turned out to be a trivial alternative solution. I wanted to share this solution in case it's useful for someone else.

@m5rk
Copy link

m5rk commented Nov 19, 2013

You may want to checkout chamber, which supports an arbitrary number of files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants