4. Now you can edit your config file and strip it down to the only settings which are not possible to control in the database. e.g., the Postgres and webserver (Endpoint) settings cannot be controlled in the database because the application needs the settings to start up and access the database.
⚠️ **THIS IS NOT REQUIRED**
Any settings in the database will override those in the config file, but you may find it less confusing if the setting is only declared in one place.
3. Edit your Pleroma config to enable database configuration:
A non-exhaustive list of settings that are only possible in the config file include the following:
```
config :pleroma, configurable_from_database: true
```
* config :pleroma, Pleroma.Web.Endpoint
* config :pleroma, Pleroma.Repo
* config :pleroma, configurable_from_database
* config :pleroma, :database, rum_enabled
* config :pleroma, :connections_pool
4. ⚠️ **THIS IS NOT REQUIRED** ⚠️
Here is an example of a server config stripped down after migration:
Now you can edit your config file and strip it down to the only settings which are not possible to control in the database. e.g., the Postgres (Repo) and webserver (Endpoint) settings cannot be controlled in the database because the application needs the settings to start up and access the database.
```
use Mix.Config
Any settings in the database will override those in the config file, but you may find it less confusing if the setting is only declared in one place.