Synchronize frontend plugin configuration

README.md

@@ -51,6 +51,19 @@ Set secure MariaDB passwords in `.env`. Then, set at least these values in
         "provider": "hcaptcha",
         "secret": "replace with your hCaptcha secret"
     },
+    "plugins": [
+        "announcement",
+        "application",
+        "banner",
+        "challenge",
+        "division",
+        "downloads",
+        "economy",
+        "event",
+        "poll",
+        "route",
+        "task"
+    ],
     "external_plugins": ["client-config"]
 }
 ```
@@ -68,6 +81,16 @@ Create an hCaptcha site for the public frontend domain. Set its secret in the
 `captcha.secret` value. Set the related public site key as
 `VITE_HCAPTCHA_SITEKEY` in the frontend deployment.
 
+The upstream sample uses plural names for some built-in plugins, but the
+backend expects the singular names shown above. This deployment configuration
+enables all built-in plugins by default. Keep `client-config` separate in
+`external_plugins`.
+
+The deployment patch synchronizes the plugin list from `config/config.json` to
+the stored frontend configuration when the backend starts. Other frontend
+settings in MariaDB stay unchanged. Restart the backend after you enable or
+disable a plugin.
+
 ## Start the deployment
 
 ```bash