4fcf272717
Since python doesn't have a way to lock deps for a particlar project by default, I didn't bother with it. This resulted in mkdocs updating at some point, bringing a breaking change to how tabs are declared and broken tabs on docs-develop.pleroma.social. I've learned my lesson and locked deps with pipenv in pleroma/docs!5. This MR updates Pleroma docs to use the new tab style, fortunately my editor did most of it. Closes #2045
1 KiB
1 KiB
Transfering the config to/from the database
{! backend/administration/CLI_tasks/general_cli_task_info.include !}
Transfer config from file to DB.
!!! note You need to add the following to your config before executing this command:
```elixir
config :pleroma, configurable_from_database: true
```
=== "OTP"
```sh
./bin/pleroma_ctl config migrate_to_db
```
=== "From Source"
```sh
mix pleroma.config migrate_to_db
```
Transfer config from DB to config/env.exported_from_db.secret.exs
!!! note In-Database configuration will still be applied after executing this command unless you set the following in your config:
```elixir
config :pleroma, configurable_from_database: false
```
To delete transfered settings from database optional flag -d can be used. <env> is prod by default.
=== "OTP"
sh ./bin/pleroma_ctl config migrate_from_db [--env=<env>] [-d]
=== "From Source"
sh mix pleroma.config migrate_from_db [--env=<env>] [-d]