Plugin Management
Plugin management is the central place in the admin area where you can activate, deactivate and inspect installed plugins in detail. The interface is intentionally kept simple.
On this page
Opening Plugin Management
Plugin management is exclusively accessible to admins. You can find it in the left navigation bar of FediSuite under Admin Area → Plugins.
Navigation in FediSuite
The Plugin List
Plugin management shows all plugins that FediSuite found and loaded in the mounted plugins folder. Each plugin appears as its own card with the most important information at a glance.
Adds Bluesky as an additional platform with account connection, publishing, import and statistics updates.
Version: 1.0.0 · Author: FediSuite OSS
Each plugin card shows at a glance:
Name
The display name of the plugin — e.g. "Bluesky Provider".
Status Badge
Shows the current runtime status: RUNNING, STOPPED or ERROR. Details below.
Description
Brief explanation of what the plugin does and which features it adds.
Version & Author
The version number of the plugin and who developed it.
Action Buttons
"Activated" indicates the plugin is currently active. "Deactivate" turns it off. If a plugin is inactive, an "Activate" button appears instead.
Arrow (▼ / ▲)
Expands or collapses the detail view of the plugin.
Activating and Deactivating Plugins
Activating and deactivating plugins is the only action you perform in plugin management. The process is straightforward.
Activate a plugin
If a plugin is installed but deactivated, an Activate button appears. A click on it enables the plugin immediately.
Deactivate a plugin
When a plugin is actively running, the Deactivate button appears. A click turns off the plugin without deleting it.
What happens when activating / deactivating?
FediSuite activates the plugin. The features provided by the plugin — e.g. the Bluesky provider — are now available.
No restart required.FediSuite deactivates the plugin. The plugin features are no longer available. The plugin files on the server remain intact — the plugin can be re-activated at any time.
No restart required.plugins/ folder on the server remain intact. To fully remove a plugin, delete its folder on the server and restart the containers — as described on the Installing Plugins page.
Reloading Plugins
In the top right of plugin management there is a Reload button. It tells FediSuite to re-read the plugins folder and refresh the plugin list in the interface.
When is "Reload" useful?
Viewing Plugin Details
Each plugin card can be expanded by clicking the arrow (▼). In the expanded view you'll find technical details about the plugin — useful when you want to check which version is loaded, where the plugin was installed or what permissions it requires.
Adds Bluesky as an additional platform with account connection, publishing, import and statistics updates.
Version: 1.0.0 · Author: FediSuite OSS
1
Compatible
Loaded
No restart required
GPL-3.0-or-later
/app/plugins/fedisuite-plugin-bluesky
./server/index.js
./web/manifest.json
5/2/2026, 00:19:54
5/2/2026, 00:19:54
—
—
Capabilities
providerRequired Permissions
Required Environment Variables
No required environment variables specified.
What do the individual fields mean?
General
Plugin API
The version of the plugin API this plugin uses. If it does not match the version supported by FediSuite, the plugin will be marked as incompatible.
Runtime Status
Shows whether the plugin is currently loaded in memory. "Loaded" means it is active and running. Other possible values: "Not loaded", "Error".
Compatibility
"Compatible" means the plugin works with the installed FediSuite version. If incompatible, the plugin should be updated to a newer version.
Restart required
Indicates whether a container restart is required for a change to the plugin status. Typically: "No restart required".
License
The software license of the plugin. All official FediSuite plugins are licensed under GPL-3.0-or-later.
Paths & Entry Points
Installation path
The absolute path in the container where the plugin is mounted. Corresponds to /app/plugins/ followed by the plugin folder name.
Server entry
The relative path to the JavaScript file that FediSuite loads on the server side at startup. Typically ./server/index.js.
Web entry
The relative path to the manifest file for the browser-side plugin component. Typically ./web/manifest.json.
Timestamps
Last updated
Date and time of the last file change in the plugin folder. Changes when you run git pull.
Last loaded
The time FediSuite last read the plugin — typically at the last container start or after a "Reload".
Capabilities & Permissions
Capabilities
Describes what kind of extension the plugin provides. "provider" means the plugin adds a new platform (like Bluesky) as a connectable source.
Required Permissions
System-internal permissions the plugin requests. "providers" allows registering a new provider, "web.runtime" allows embedding browser-side components.
Required Environment Variables
If a plugin expects specific entries in .env, they are listed here. If none are listed, no additional configuration is needed.
Understanding Status Badges
Each plugin card carries a colored status badge that shows the current state of the plugin at a glance.
The plugin is active, was loaded successfully and is running without errors. All features provided by the plugin are available.
The plugin is installed but manually deactivated. It was shut down properly and can be re-activated at any time.
An error occurred while loading the plugin. Possible causes: the plugin files are corrupted, the plugin API version is incompatible or a required resource is missing. Container logs (docker compose logs app) provide more details.
The plugin API version of the plugin does not match the version supported by FediSuite. Update the plugin (git pull in the plugins/ folder) to fix the problem.