From 55ceb128aebc2ff3d580d2e655a94902fed702b2 Mon Sep 17 00:00:00 2001 From: FloatingGhost Date: Thu, 14 Jul 2022 15:05:53 +0100 Subject: [PATCH] Put frontend options under a category --- docs/configuration/cheatsheet.md | 2 ++ docs/configuration/frontend_management.md | 6 +++--- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/configuration/cheatsheet.md b/docs/configuration/cheatsheet.md index 17da58594..e3f862783 100644 --- a/docs/configuration/cheatsheet.md +++ b/docs/configuration/cheatsheet.md @@ -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). diff --git a/docs/configuration/frontend_management.md b/docs/configuration/frontend_management.md index 077fd9c31..522cd37c5 100644 --- a/docs/configuration/frontend_management.md +++ b/docs/configuration/frontend_management.md @@ -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" } ```