Settings constant is a singleton shared across all request to your Rails app. That means it would load your client config once when the server starts (single Rails server instance serving single client). Is this what you are trying to achieve?

In contrast you might want to apply custom client settings per every request, so one server can respond to multiple clients...

@pkuczynski it would be nice improvement in terms of splitting different config files by domains/technologies. Big config file is difficult for reading/understanding, is there a chance for implementing this feature?

@IlyaKorol you can add sources in runtime. It should not be hard to do the same on the initializer level as @DannyBen suggested:

Config.setup do |config|
  config.const_name = "Settings"
  config.extra_sources = [...]
end

Feel free to create PR for this feature and we will merge it.

This is an interesting idea!

Not saying this PR should do it, but I'm wondering if we can extend this to also include non-file-based sources as well. For example, in our app we have a custom source type that points to a database table, so we can store user-driven changes to the settings. It would be cool to be able to inject that in as well by just passing the object to extra_sources.