logo

pleroma

My custom branche(s) on git.pleroma.social/pleroma/pleroma git clone https://hacktivis.me/git/pleroma.git

howto_database_config.md (4702B)

    

  1. # How to activate Pleroma in-database configuration
  2. ## Explanation
  4. The configuration of Pleroma has traditionally been managed with a config file, e.g. `config/prod.secret.exs`. This method requires a restart of the application for any configuration changes to take effect. We have made it possible to control most settings in the AdminFE interface after running a migration script.
  6. ## Migration to database config
  8. 1. Run the mix task to migrate to the database.
  10.   **Source:**
  12.   ```
  13.   $ mix pleroma.config migrate_to_db
  14.   ```
  16.   or
  18.   **OTP:**
  20.   *Note: OTP users need Pleroma to be running for `pleroma_ctl` commands to work*
  22.   ```
  23.   $ ./bin/pleroma_ctl config migrate_to_db
  24.   ```
  26.   ```
  27.     Migrating settings from file: /home/pleroma/config/dev.secret.exs
  29.    Settings for key instance migrated.
  30.    Settings for group :pleroma migrated.
  31.   ```
  33. 2. It is recommended to backup your config file now.
  35.   ```
  36.   cp config/dev.secret.exs config/dev.secret.exs.orig
  37.   ```
  39. 3. Edit your Pleroma config to enable database configuration:
  41.   ```
  42.   config :pleroma, configurable_from_database: true
  43.   ```
  45. 4. ⚠️ **THIS IS NOT REQUIRED** ⚠️
  47.   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.
  49.   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.
  51.   A non-exhaustive list of settings that are only possible in the config file include the following:
  53.   * config :pleroma, Pleroma.Web.Endpoint
  54.   * config :pleroma, Pleroma.Repo
  55.   * config :pleroma, configurable\_from\_database
  56.   * config :pleroma, :database, rum_enabled
  57.   * config :pleroma, :connections_pool
  59.   Here is an example of a server config stripped down after migration:
  61.   ```
  62.   import Config
  64.   config :pleroma, Pleroma.Web.Endpoint,
  65.     url: [host: "cool.pleroma.site", scheme: "https", port: 443]
  67.   config :pleroma, Pleroma.Repo,
  68.     adapter: Ecto.Adapters.Postgres,
  69.     username: "pleroma",
  70.     password: "MySecretPassword",
  71.     database: "pleroma_prod",
  72.     hostname: "localhost"
  74.   config :pleroma, configurable_from_database: true
  75.   ```
  77. 5. Restart your instance and you can now access the Settings tab in AdminFE.
  80. ## Reverting back from database config
  82. 1. Run the mix task to migrate back from the database. You'll receive some debugging output and a few messages informing you of what happened.
  84.   **Source:**
  86.   ```
  87.   $ mix pleroma.config migrate_from_db
  88.   ```
  90.   or
  92.   **OTP:**
  94.   ```
  95.   $ ./bin/pleroma_ctl config migrate_from_db
  96.   ```
  98.   ```
  99.   10:26:30.593 [debug] QUERY OK source="config" db=9.8ms decode=1.2ms queue=26.0ms idle=0.0ms
  100.   SELECT c0."id", c0."key", c0."group", c0."value", c0."inserted_at", c0."updated_at" FROM "config" AS c0 []
  102.   10:26:30.659 [debug] QUERY OK source="config" db=1.1ms idle=80.7ms
  103.   SELECT c0."id", c0."key", c0."group", c0."value", c0."inserted_at", c0."updated_at" FROM "config" AS c0 []
  104.   Database configuration settings have been saved to config/dev.exported_from_db.secret.exs
  105.   ```
  107. 2. Remove `config :pleroma, configurable_from_database: true` from your config. The in-database configuration still exists, but it will not be used. Future migrations will erase the database config before importing your config file again.
  109. 3. Restart your instance.
  111. ## Debugging
  113. ### Clearing database config
  114. You can clear the database config with the following command:
  116.   **Source:**
  118.   ```
  119.   $ mix pleroma.config reset
  120.   ```
  122.   or
  124.   **OTP:**
  126.   ```
  127.   $ ./bin/pleroma_ctl config reset
  128.   ```
  130. Additionally, every time you migrate the configuration to the database the config table is automatically truncated to ensure a clean migration.
  132. ### Manually removing a setting
  133. If you encounter a situation where the server cannot run properly because of an invalid setting in the database and this is preventing you from accessing AdminFE, you can manually remove the offending setting if you know which one it is.
  135. e.g., here is an example showing a the removal of the `config :pleroma, :instance` settings:
  137.   **Source:**
  139.   ```
  140.   $ mix pleroma.config delete pleroma instance
  141.   Are you sure you want to continue? [n]  y
  142.   config :pleroma, :instance deleted from the ConfigDB.
  143.   ```
  145.   or
  147.   **OTP:**
  149.   ```
  150.   $ ./bin/pleroma_ctl config delete pleroma instance
  151.   Are you sure you want to continue? [n]  y
  152.   config :pleroma, :instance deleted from the ConfigDB.
  153.   ```
  155. Now the `config :pleroma, :instance` settings have been removed from the database.