everzet
Hi everyone.
I’ve been reading about the upcoming releases feature in 1.9. In the runtime configuration section, there is one paragraph that caught my attention. It basically suggests that the release in production is going through the following steps on boot:
- Erlang system starts in limited mode, without booting core app supervision tree
- Registered config providers are used to aggregate and merge configs into one big set
- Config set is stored on disk under the RELEASE_TMP directory
- Erlang system reboots in full mode, reads the config file and boots app supervision tree
If this is correct, I have a question. Why the file interaction? Why can’t we start a lightweight GenServer process or an agent within Beam and use it to store and retrieve the runtime configuration instead?
Can somebody please point me in direction of context I am missing? 
Where Next?
Trending in Discussions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Elixir, Erlang & messaging conferences from Code Sync. Next up: ElixirConf US (10–11 Sep) & Code BEAM Europe (21–22 Oct), Haarlem + online.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
josevalim
We can’t because the configuration is used to configure the system itself, at its core. So you can think that, at the moment the configuration is read, a GenServer isn’t even a thing yet.
everzet
I was under (probably wrong) impression that the configuration only impacts the userland processes and supervision trees.
If that (probably wrong) assumption was true, I imagined you can delay the boot of userland supervision trees and boot the separate config process, with its own supervisor, before starting the application, for example.
What you are saying is that there are some configs that go beyond just your userland supervision trees and impact the beam itself. Is it right?
josevalim
Not the beam itself but the kernel and stdlib applications, which are started before everything else in your code.
everzet
Oh. I am starting to understand now.
Let me check I am getting it right. You are saying there are fundamental processes of Elixir stdlib and kernel that are booted as part of system load (not by user intention) and which can’t be reloaded without restarting the whole thing. Right?
josevalim
Yes!!!
everzet
Thank you for sticking with me on this one
Very much appreciate your time and patience.