SwissKnife Docs
Operate SwissKnife

Update and rollback

Record the running digest, pull a new image, and restore a previous pin.

SwissKnife stores no application data. An update replaces the static files inside the container. There is nothing to back up except the Compose file and the image pin you chose.

Record the current image

docker compose images
docker image inspect --format '{{.RepoDigests}}' ghcr.io/lucas-lepajollec/swissknife:latest

Keep that digest or the sha-<full-commit> tag. That is the rollback target.

Update

docker compose pull
docker compose up -d
docker compose ps

Confirm the container becomes healthy and that http://127.0.0.1:2501 still serves the application.

Roll back

Change the Compose image: line to the previous tag or digest, then recreate the container:

image: ghcr.io/lucas-lepajollec/swissknife:sha-<full-commit>
docker compose up -d

Do not recreate a v1.0.0 tag to recover an old instance. Use a recorded digest or sha- tag.

Backup

N/A as application state: selected files and conversion results live only in the browser tab. Back up your Compose override and image pin if you need to rebuild the same instance.

On this page