Configuration
Where settings come from
Section titled “Where settings come from”From lowest to highest priority:
- Built-in defaults.
- A TOML file:
<data_dir>/dogubako.toml, or the file given with--configorDOGUBAKO_CONFIG. Start fromdeploy/dogubako.example.toml. - Environment variables:
DOGUBAKO_plus the key in upper case, for examplemax_upload_mbisDOGUBAKO_MAX_UPLOAD_MB. - Command-line flags:
--bind,--data-dir,--config,--public-url,--no-auth.
dogubako server config prints the effective configuration as TOML, which is
the quickest way to check what the server will use.
# <data_dir>/dogubako.tomlbind = "0.0.0.0:8420"public_url = "https://tools.example.com"instance_name = "Home toolbox"secure_cookies = truemax_upload_mb = 4096file_retention_hours = 48sandbox = "bwrap"Every setting is listed in the configuration reference.
Common setups
Section titled “Common setups”A household server
Section titled “A household server”A few trusted people, files kept for a couple of days:
DOGUBAKO_INSTANCE_NAME="Home toolbox"DOGUBAKO_FILE_RETENTION_HOURS=72DOGUBAKO_USER_QUOTA_MB=20480A shared server for AI agents
Section titled “A shared server for AI agents”Many agents, mostly short jobs, tight isolation:
DOGUBAKO_MCP_DISCOVERY=compact # agents search for tools instead of listing all 249DOGUBAKO_PER_USER_CONCURRENCY=1DOGUBAKO_USER_QUOTA_MB=2048DOGUBAKO_FILE_RETENTION_HOURS=6DOGUBAKO_SANDBOX=bwrap # native Linux installsA video and transcription box
Section titled “A video and transcription box”Few users, long CPU-heavy jobs:
DOGUBAKO_MAX_CONCURRENT_JOBS=2 # FFmpeg and whisper.cpp use several threads eachDOGUBAKO_MAX_JOB_SECONDS=14400 # four hoursDOGUBAKO_EXEC_CPU_SECS=14400DOGUBAKO_EXEC_MEMORY_MB=8192DOGUBAKO_MAX_UPLOAD_MB=8192Keep the container or service memory limit above
EXEC_MEMORY_MB × MAX_CONCURRENT_JOBS.
Folder tools on a NAS
Section titled “Folder tools on a NAS”Let tools such as duplicate finders and folder size read your shares:
DOGUBAKO_FS_ROOTS=/srv/photos,/srv/documentsThen grant host_fs_read to the accounts that should use them. Paths are
resolved (symlinks included) and must stay inside a root.
Engine paths
Section titled “Engine paths”Point the server at a specific engine binary with DOGUBAKO_<ID>_PATH, for
example DOGUBAKO_FFMPEG_PATH=/opt/ffmpeg/bin/ffmpeg. The ids are listed in
Engines and models.