Updating

Updating Printbuddy

Recommendation: take a backup before upgrading. In the UI, use Settings → Backup → Create Backup. Docker/manual upgrades do not automatically create a backup.

Docker / Docker Compose

Make sure your compose file points to the Printbuddy image:

image: docker.io/vmhomelabde/printbuddy:latest

Then pull and restart:

docker compose pull
docker compose up -d

If you want Printbuddy administrators to trigger this from the web UI, configure the optional self-update sidecar. The main Printbuddy container does not receive Docker socket access; only the updater sidecar can call Docker Compose.

For the development/test channel, use:

image: docker.io/vmhomelabde/printbuddy:dev

Refresh an old compose file

If your docker-compose.yml is old or still references the pre-fork project, download a fresh compose file from the Printbuddy repository and diff it against yours:

curl -fsSL https://raw.githubusercontent.com/vmhomelab/Printbuddy/main/docker-compose.yml   -o docker-compose.yml.new

diff -u docker-compose.yml docker-compose.yml.new || true

Merge your local settings into the new file, then restart:

docker compose up -d

Do not pull ghcr.io/maziggy/bambuddy:latest for Printbuddy.

Native install

Preferred update command:

sudo /opt/printbuddy/install/update.sh

Manual equivalent:

cd /opt/printbuddy
sudo systemctl stop printbuddy
sudo -u printbuddy git fetch origin
sudo -u printbuddy git reset --hard origin/main
sudo -u printbuddy venv/bin/pip install -r requirements.txt
sudo systemctl start printbuddy

Replace /opt/printbuddy with your install path if different.