2 You can configure your instance from admin interface. You need account with admin rights and little change in config file, which will allow settings configuration from database.
5 config :pleroma, configurable_from_database: true
9 Settings are stored in database and are applied in `runtime` after each change. Most of the settings take effect immediately, except some, which need instance reboot. These settings are needed in `compile time`, that's why settings are duplicated to the file.
11 File with duplicated settings is located in `config/{env}.exported_from_db.exs`. For prod env it will be `config/prod.exported_from_db.exs`.
14 You need to migrate your existing settings to the database. You can do this with mix task (all config files will remain untouched):
16 mix pleroma.config migrate_to_db
18 Now you can change settings in admin interface. After each save, settings are duplicated to the `config/{env}.exported_from_db.exs` file.
20 <span style="color:red">**ATTENTION**</span>
22 **<span style="color:red">Be careful while changing the settings. Every inaccurate configuration change can break the federation or the instance load.</span>**
24 *Compile time settings, which require instance reboot and can break instance loading:*
25 - all settings inside these keys:
28 - `Pleroma.Web.Endpoint`
29 - partially settings inside these keys:
30 - `:seconds_valid` in `Pleroma.Captcha`
31 - `:proxy_remote` in `Pleroma.Upload`
32 - `:upload_limit` in `:instance`
36 1. Truncate or delete all values from `config` table
38 TRUNCATE TABLE config;
40 2. Delete `config/{env}.exported_from_db.exs`.
45 cp config/prod.exported_from_db.exs config/exported_from_db.back
46 rm -rf config/prod.exported_from_db.exs
48 *If you don't want to backup settings, you can skip step with `cp` command.*
50 3. Set configurable_from_database to `false`.
52 config :pleroma, configurable_from_database: false
54 4. Restart pleroma instance
56 sudo service pleroma restart