Put frontend options under a category
ci/woodpecker/push/release Pipeline was successful Details
ci/woodpecker/push/lint Pipeline was successful Details
ci/woodpecker/pr/lint Pipeline was successful Details
ci/woodpecker/pr/release Pipeline was successful Details
ci/woodpecker/pr/test Pipeline was successful Details
ci/woodpecker/push/test Pipeline was successful Details

This commit is contained in:
FloatingGhost 2022-07-14 15:05:53 +01:00
parent bcdbbad037
commit 55ceb128ae
2 changed files with 5 additions and 3 deletions

View File

@ -249,6 +249,8 @@ Notes:
* `total_user_limit`: the number of scheduled activities a user is allowed to create in total (Default: `300`)
* `enabled`: whether scheduled activities are sent to the job queue to be executed
## Frontend Management
### :frontend_configurations
This can be used to configure a keyword list that keeps the configuration data for any kind of frontend. By default, settings for `pleroma_fe` and `masto_fe` are configured. You can find the documentation for `pleroma_fe` configuration into [Pleroma-FE configuration and customization for instance administrators](/frontend/CONFIGURATION/#options).

View File

@ -13,11 +13,11 @@ Example:
```elixir
config :pleroma, :frontends,
primary: %{
"name" => "pleroma",
"ref" => "stable"
"name" => "pleroma-fe",
"ref" => "develop"
},
admin: %{
"name" => "admin",
"name" => "admin-fe",
"ref" => "develop"
}
```