Skip to main content

FUME_PLUGINS_CONFIG

Applies to​

  • Enterprise 3.3.0+

Default​

Unset. No plugin workers or plugin functions/routes are created.

Examples​

FUME_PLUGINS_CONFIG=/etc/fume/plugins/deployment.yaml

Purpose​

Selects an explicit local JSON or YAML deployment file for administrator-installed native plugins. The setting is a filesystem path, not inline base64, a URL or an npm package name. A relative setting resolves from the server working directory; plugin paths inside the file resolve from the deployment file's directory.

Notes​

  • An explicit missing, malformed or invalid deployment fails startup with a safe error. No default file is discovered automatically.
  • Deploy immutable .cjs artifacts and restart after changing the deployment, artifacts or secrets. There is no upload, hot reload or automatic package installation.
  • Environment-backed factory secrets use each installation's configEnv map. Factory configuration does not become expression bindings.
  • Mount deployment files, artifacts and supporting files read-only. Child processes run administrator-trusted code, not a hostile-code sandbox.
  • See Configuration and secrets for the full schema and Quickstart for a runnable deployment.