Where Does Laminar CI Store Config and Runs?
Laminar reads /etc/laminar.conf and keeps jobs plus run archives under /var/lib/laminar. Back up both halves.
Last updated
Laminar centers on two paths. The /etc/laminar.conf file holds daemon settings including LAMINAR_HOME, bind address, and mail. The home tree (default /var/lib/laminar) holds job scripts, per-run archives, and resources. Completed runs clean up by default, keeping only archived artefacts the job chose to save.
That ephemeral-by-default design shapes backups: copy the conf plus the home tree and you keep definitions plus kept artefacts, nothing more. Package installs create a laminar user with a systemd unit; Docker layouts bind both paths from the host. Job logic itself lives in scripts, which belong in version control beside the backup, not inside it.
Where Laminar stores this, by platform
/etc/laminar.conf
Daemon settings including LAMINAR_HOME base path and bind address. Package installs create a laminar user plus systemd unit. Back with the home tree as one unit.
/var/lib/laminar (LAMINAR_HOME)
Job scripts, run archives, resources. Completed runs prune to archived artefacts only. LAMINAR_HOME relocates the whole tree; Docker binds both paths from the host.
Frequently asked questions
how do i back up laminar ci
Copy /etc/laminar.conf plus /var/lib/laminar (jobs, run archives, resources) with the daemon stopped. Job scripts version in git separately, so the folder plus repo is the complete restore.
can i move the laminar home directory
Set LAMINAR_HOME in /etc/laminar.conf to the new path and move the tree with the daemon stopped. The daemon resolves everything relative to that base, so one variable moves jobs, runs, and resources together.
Notice an outdated path? Let us know.