Let's suppose we have a elixir service that spawns some workers to do a job, the supervisor takes configuration from config and starts the workers. Now the classic way to configure such a project in prod is to use *releases.exs*, where you can configure environment variables and the release will reload the configuration*.*
What I want to implement now is a dashboard that will control multiple services configuration, this means that there should be a centralized storage for configuration and some kind of signaling when to change configuration. Let's suppose we use postgres, some tables to store the configuration and custom signaling/ postgres NOTIFY to notify that the configuration has changed and needs to be reloaded. The questions that arise are: 1. Is it possible/recommended to change the *releases.exs *file responsible for configuration in a release so that the new configuration is persisted across reloads? 2. Is it possible to implement this for dev environment? since as far as I know dev environment does not support runtime configuration currently. 3. Is it intended behavior that *releases.exs *replaces configuration added with *Application.put_env/4 *with option *persistent: true*? -- 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 elixir-lang-core+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/d274f872-3b2a-48ed-880e-363c36dcda36n%40googlegroups.com.
