Deploy Starling plugins

Starling runs plugins inside its plugins service. Native plugin libraries and WebAssembly components use the host’s scoped capabilities for configuration, sessions, channels, permissions, and messaging.

The service reads its host options from [services.plugins.options]. Configure plugins_dir to the directory containing compatible plugin artifacts. With no directory configured, no plugins are loaded.

[services.plugins.options]
plugins_dir = "/var/lib/starling/plugins"

Per-plugin settings use the plugin.<name>. prefix inside that options table. Read the plugin’s own documentation for its keys. After startup, check the service logs and advertised registry; a plugin file on disk does not prove that it loaded successfully.

The host supports listing, enabling, disabling, and uninstalling loaded plugins. Installation from remotely uploaded bytes and the operator REST plugin routes remain unfinished in the current host plan. Place artifacts through your deployment tooling and use only the administration operations supported by your release.

See the plugin host implementation and plan, Starling configuration reference, and feature availability.