Updating vuzon

The image is rebuilt and published on every release. Updating is one command; your .env is untouched and sessions survive the restart.

Update

$ docker compose pull && docker compose up -d

The image is rebuilt and published to GHCR on every release, multi-arch amd64 / arm64. Your .env is untouched; sessions survive the restart.

With the latest tag, that command brings the newest published image — including a new major version, and a major is where breaking changes live. Skim the release notes before you run it. To decide when a major jump happens, pin a concrete version on the image: line and bump it yourself.

Upgrading from 1.x

The panel credentials moved out of .env in 2.0:

• AUTH_USER, AUTH_PASS and SESSION_SECRET are ignored from 2.0 on — delete all three from your .env.
• The first time you open the updated panel it shows the setup wizard and asks you to choose credentials again — this time stored hashed in the vuzon-data volume.
• Add the vuzon-data volume to your docker-compose.yml if you are reusing an older copy of the file.