Where Does Liquidsoap Keep Scripts and Logs?
Liquidsoap scripts, logs and cache on Linux, systemd units, and the --check habit that saves stations.
Last updated
Liquidsoap production layout is refreshingly standard on Linux. Scripts (.liq) live in /etc/liquidsoap, logs stream to /var/log/liquidsoap, and a package cache sits in /var/cache/liquidsoap. Distro packages create a liquidsoap user and group to run it all.
The workflow that matters is check before restart. Scripts edit live radio, so the --check flag plus a systemd unit turns cowboy deploys into boring ones. Logrotate ships configured; leave the log path alone.
Where Liquidsoap stores this, by platform
/etc/liquidsoap
Production scripts live here; start them via systemd or the init script, which daemonizes automatically. Validate with liquidsoap --check before every restart. Cache and logs sit in /var/cache and /var/log siblings.
Frequently asked questions
How do I test a Liquidsoap script safely?
Run liquidsoap --check against the script before restarting the service. It parses and type checks without going live, catching errors while the old instance still plays.
Where are Liquidsoap logs?
Under /var/log/liquidsoap named per script, with logrotate configured by the packages. Do not override the log path; the shipped rotation expects the standard directory.
How do I run Liquidsoap at boot?
As a systemd unit running as the liquidsoap user, typically /etc/systemd/system/radio.service. Enable it and the station survives reboots and crashes automatically.
Notice an outdated path? Let us know.