Upgrading
How you upgrade depends on how you installed Lamb. There is more information about branches to be on — release is the stable branch.
Git install
Run the bundled upgrade script:
bin/upgrade
It resets your checkout to the latest version of the branch you are on, installs production dependencies, and — when SITE_URL is set in .env — checks that the site still responds. If the health check fails, it prints the exact command to roll back to the previous version.
Note: the reset discards any local changes to tracked files. Your database (data/), uploads (src/assets/), and .env are not tracked, so they are unaffected.
To upgrade automatically every night, add it to cron:
15 3 * * * /path/to/lamb/bin/upgrade
Cron will email you the output if the health check fails (when your system is set up to deliver mail).
Tarball install
Download the latest lamb-<version>.tar.gz from the releases page and extract it over your existing installation:
tar -xzf lamb-<version>.tar.gz --strip-components=1 -C /path/to/lamb
Your database (data/), uploads (src/assets/), and .env are preserved — the tarball does not contain them.
Docker install
Pull the new image and recreate the container:
docker pull ghcr.io/svandragt/lamb:latest
docker stop lamb && docker rm lamb
docker run -d --name lamb -p 80:80 \
-e LAMB_LOGIN_PASSWORD='<your-hash>' \
-v lamb-data:/app/data -v lamb-assets:/app/src/assets \
ghcr.io/svandragt/lamb:latest
The database and uploads live in the named volumes and survive the recreate.