File Configuration
Carry file notes, webhooks, and MCP server settings along with a build so they are applied automatically to the destination server.
File notes, webhooks, and MCP server settings attached to your files can travel with a build and be applied to the destination server automatically during a deployment. This means you do not need to manually recreate that configuration on the destination server after moving a file.
File Configuration requires OttoFMS 4.17.0 or later on both the source and destination server.
Collecting File Configuration on a Build
On a build, turn on Collect File Configuration to gather configuration from the source server. This has three sub-toggles:
- File Notes — collects file notes attached to your files.
- Webhooks — collects webhooks, optionally limited to specific channels.
- MCP Servers — collects MCP server settings, optionally limited to specific servers and tools.
Leave a filter empty to collect everything of that type.
Deploying File Configuration
On a deployment, the default file options include a Deploy File Configuration setting with the same File Notes, Webhooks, and MCP Servers sub-options. You can override this setting on a per-file basis if you need different behavior for specific files.
File Configuration is applied after the rest of the deployment finishes, so it will not cause an otherwise successful deployment to fail.
Was this page helpful?