Updating PalCenter

Updating PalCenter

PalCenter data is stored separately from the container in /app/data. Recreating the container with the same volume preserves configuration, users, history, notifications, and the internal session secret.

Recommended upgrade process

1. Sign in and create a current backup from Backup & Restore.
2. Record the image tag and UID/GID currently in use.
3. Review the release notes.
4. Change the image tag in docker-compose.yml.
5. Pull and recreate the container:

docker compose pull
docker compose up -d

6. Check the container health and logs:

docker compose ps
docker compose logs --tail=100 palcenter

7. Sign in and confirm servers, notifications, users, and history.

Do not run docker compose down -v; the -v option deletes named volumes.

Pinned releases and latest

For predictable upgrades, use a release tag:

image: ghcr.io/shanebionic/palcenter:v1.1.1

The latest tag follows the newest published release but can change the next time you pull.

Rollback

If an upgrade fails:

1. Stop PalCenter.
2. Restore the previous image tag.
3. Recreate the container with the same volume.
4. If required, restore the backup created before the upgrade.

Never delete or replace /app/data unless you intend to restore it.