Where Does Snikket Store Config and Data?
Snikket keeps host config in /etc/snikket on Linux with all server data in a Docker volume mounted at /snikket. Logs stream to stdout.
Last updated
Snikket organizes hosting into two places. The host contributes /etc/snikket with the environment config and compose files. Docker contributes a named volume carrying the /snikket tree with Prosody data, certs and proxy state.
Logs refuse to sit still as files. Prosody writes to stdout for compose to collect, with certificate troubleshooting as the one exception tucked inside its container. Back up config plus volume and ignore log files that were never there.
Where Snikket stores this, by platform
/etc/snikket/snikket.conf
Host environment config with domain and admin variables plus the compose file downloaded from official resources. Extra config globs in through the tweak variable. The generated Prosody config inside the image stays hands-off.
/var/lib/docker/volumes/snikket_data/_data
Named-volume storage with Prosody data beneath it, shared across proxy, certs and server containers. Persist around 10GB per community guidance. Logs stream to stdout rather than files here.
Frequently asked questions
How do I back up a Snikket server?
Archive /etc/snikket with its conf and compose files plus the snikket_data volume holding /snikket with Prosody data. Community guidance calls for persisting around 10GB for the volume. Logs stream to stdout, so capture compose output rather than copying log files.
Where is the Snikket config file?
Edit /etc/snikket/snikket.conf with domain, admin email and tweak variables, then recreate the stack. Extra Prosody configuration arrives through the dedicated tweak variable pointing at additional files. The generated Prosody config inside the image is not hand-edited.
Where are Snikket logs?
Read them from compose output. Prosody logs to stdout with verbosity from the loglevel variable, while certificate issues hide in the certs container letsencrypt logs. No host log directory exists to browse.
Notice an outdated path? Let us know.