Support dynamic configuration in SQL
This is a requirement to support Pleroma configuration in AdminFE. Here is the current idea:
Possible API endpoint:
GETshould return the existing config (if any) in the database.
- Bonus if we can provide an additional parameter to get the configuration back in a format that is usable in the config file again.
POSTshould allow writing the config to the database
- Mix tasks for forward and reverse migration of the config
Obviously we can't store the database settings (
config :pleroma, Pleroma.Repo) in the database, but everything else should be possible.
For simplicity we should make the database configuration override any existing config file settings if they both exist and conflict with each other.