Configuration

Middlewarr reads data/settings.yml relative to its working directory. In the supplied container, that is /data/settings.yml. The file is required; startup fails if it cannot be loaded.

Minimal configuration

host: 0.0.0.0

auth:
  cookieSecure: false

templates:
  repository: https://github.com/middlewarr/templates
  branch: main

Restart the container after changing this file. Services, apps, proxies, notification destinations, and template-source records are managed in the dashboard and stored in SQLite.

Settings reference

Setting	Behavior
host	Address the server binds to. Use 0.0.0.0 inside the container for published-port access.
auth.cookieSecure	Adds the Secure attribute to the administration session cookie. Defaults to false. Use true when the browser accesses Middlewarr over HTTPS.
templates.repository	Initial template repository URL, used only when the template-repository table is empty. Defaults to the official repository if omitted.
templates.branch	Branch for that initial source. Defaults to main if omitted.
log.level	Present in the application sample but currently ignored. Use LOG_LEVEL instead.

Template settings seed the first source; editing them later does not update existing database records. Manage sources in Settings → Templates after initialization.

The server currently listens on port 80. Change the host-side container port mapping to expose a different port; there is no supported port setting in this source snapshot.

Environment variables

Variable	Accepted value / behavior
LOG_LEVEL	Integer verbosity: -1 trace, 0 debug, 1 info, 2 warn, 3 error, 4 fatal, 5 panic, 7 disabled. Defaults to 1 when absent or not an integer.
MIDDLEWARR_RESET_ADMIN	A true Boolean value such as 1 or true clears the administrator and all sessions at startup. Remove it after recovery.
DATA_DIR	Not read by the current server. Changing it does not relocate data.

There is no general environment-variable override mechanism for settings.yml. Do not assume variables such as HOST or PORT override the file or the fixed listener.

Persistent files

Container path	Contents
/data/settings.yml	Startup settings
/data/middlewarr.db	SQLite configuration, administrator/session records, access warnings, and proxy revisions
/data/templates/	Local template repository clones
/data/openapi/	Cached service API specifications
/data/logs/	Proxy request logs and rotated files

Mount and back up the complete /data directory. It includes upstream and proxy credentials; protect it as sensitive configuration.

OpenAPI specifications

Middlewarr downloads missing service specifications during startup and reuses existing files across restarts. Settings → OpenAPI displays the cached specifications and provides a sync action.

A refresh keeps a service’s last good copy if its download or write fails. Check errors and timestamps after syncing. The specifications drive the endpoint catalog and warning-to-permission grants; they are separate from integration templates.