On Tue, 7 Mar 2017, at 10:30, José Valim wrote: > The overall design sounds correct. > > It is important to highlight that not all configuration is equal though. > We > can break them in three categories: > > * compile time - such as logger calls purging > * runtime and stateful - such as Phoenix port. If you change the port > configuration, Phoenix won't magically start listening on a new port > * runtime and stateless - when Application.get_env is called whenever it > is > needed > > So you could either have all apps reading from your config cache or have > the config system consistently read from the external service and update > Application.get_env but keep in mind some changes won't be reflected > unless > you recompile the code or restart some services.
Thanks José for the clarification. In Apache CouchDB, we wired up the configuration to the appropriate supervision trees, and exposed the runtime config via authorised RESTish API, so (for example) changing the bound IP address or port results in a restart of the mochiweb supervisor tree. This is pretty cool for long-running services like databases so you don't lose the cached file data. A+ Dave -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/1488887025.802096.903105656.579C50D2%40webmail.messagingengine.com. For more options, visit https://groups.google.com/d/optout.
