Where Does Metronome Store Config and Data?
Metronome keeps its main config at /etc/metronome on Linux with domain files beside it, plus data, upload and log trees nearby.
Last updated
Metronome mirrors Prosody in format while renaming every tree. Global config plus domain files under /etc/metronome, data under /var/lib, logs under /var/log, uploads under their own service path. The template header admits the equivalence outright.
Module files carry defaults that domain configs tune, which confuses first-time editors chasing values across layers. Validate with the lua syntax checker after edits. Upload expiry and quota settings sit with the domain files that define the service.
Where Metronome stores this, by platform
/etc/metronome/metronome.cfg.lua
Global config with domain files in conf.d beside it. Prosody-format compatible with metronome tree names. Validate syntax after edits and restart the service.
/var/lib/metronome
Server data with upload service paths nearby per domain config. Main and error logs branch under the log tree with syslog options. Module defaults live in library files.
Frequently asked questions
How do I back up Metronome config?
Copy /etc/metronome/metronome.cfg.lua with the conf.d domain files beside it. Validate syntax with the lua checker before restarts. Module defaults live in library files that the main config references rather than duplicates.
Can I reuse my Prosody config?
It shares Prosody's format exactly, as the template header states. Paths, roster and TLS blocks transfer with path swaps from prosody to metronome trees. Data and log folders differ by name and stay separate.
Where are Metronome logs and uploads?
Check /var/log/metronome for the main and error logs with syslog and console as config options. Upload expiry and quota settings live in the domain files with the upload service paths nearby.
Notice an outdated path? Let us know.