Upgrade

self-hosting

Upgrading the server is loading a new image and pointing the compose file at it. Your documentation is not involved: it lives in Git, and the server only ever reads it.

Steps

Download the new server-image.tar.gz from docucommit.se/download with your licence key.
Load it:
```
docker load < server-image.tar.gz
```
Change the tag in compose.yml to the release you just loaded — the current release is listed on the changelog:
```
image: docucommit-server:v1.0.1
```
Recreate the container:
```
docker compose up -d
```

Docker replaces the container and keeps the docucommit-repos volume, so the existing clone, licence token, users, and comments survive.

Rolling back

Old images stay on the host until you remove them, so a rollback is the same procedure with the previous tag. Keep the previous tarball until the new version has run for a while.

What upgrading cannot break

The documentation itself. Even a completely failed upgrade leaves every page where it was — in your repository, as Markdown. Worst case you serve the previous image while you work out what went wrong.