Where Does Galene Store Config and Recordings?
Galene defaults to relative data, groups and recordings folders with flags overriding. No /etc/galene exists upstream.
Last updated
Galene keeps paths relative on purpose. Data, groups, recordings and web roots default to folders under the working directory with flags overriding each. Systemd units pin the working dir so relatives resolve.
The /etc/galene path some expect simply does not exist upstream. Downstream wrappers own the only etc presence through unit files. NixOS carves its own var-lib exception. Recordings follow per-room settings with system trees protected.
Where Galene stores this, by platform
./data/config.json
Global JSON with certificates and server settings under the relative data root. Working directory decides the absolute spot with systemd pinning it. No etc path exists upstream.
./groups
Per-group JSON files with subdirectories mapping to group paths. Served recordings branch from the relative recordings root for operators. NixOS uses var-lib trees instead.
Frequently asked questions
How do I back up Galene?
Archive the data folder with certificates and JSON configs plus the groups tree with per-group files. Relative defaults resolve against the working directory, so record it alongside. Systemd units pin working dirs for this reason.
Where is /etc/galene?
It does not exist upstream. Only downstream wrappers place unit files in /etc while data stays relative. NixOS modules use var-lib trees instead. Quote relative defaults with the working directory, never an etc path.
Where do Galene recordings save?
Set recording dirs per room or filename per publish with protected system folders blocked. Served paths expose group recordings to operators only. No default directory is verified beyond the relative recordings root.
Notice an outdated path? Let us know.