Upgrading

An upgrade swaps Tesria’s software for a newer version and keeps everything you have written. A short setup step updates the database before the new version starts, so there is nothing to convert by hand. It takes a few minutes, most of them while the old version keeps running.

Before you start

• Read the Release notes for every version between yours and the new one. They say what changed and anything you need to do.

• Pick a quiet time. Tesria is unavailable for about a minute, and people with a page open may need to reload it.

Step 1: Take a backup

Choose Admin, then Backups, then Back up now, and wait until the page says the backups have finished. If the upgrade goes wrong, this is what you go back to. See Backups and recovery.

Step 2: Get the new version

If you installed Tesria with git clone, as Quick start does, run this in the Tesria folder:

git pull

Step 3: Rebuild and restart

docker compose up -d --build

Building takes a few minutes while the old version keeps running. Then the setup step updates the database and stops, each container is replaced, and Tesria is back.

Step 4: Check it

Open Admin, About (Admin is in the top bar; in a narrower window it is under More, and on a phone in the ☰ menu): it names the version now running (so does /api/health, while you are signed in). docker compose ps should show every service Up.

If something goes wrong

The logs usually say why. The first shows the setup step that updates the database, the second Tesria itself:

docker compose logs migrate
docker compose logs app

Going back means restoring the backup you took in step 1 with the version you had before. A backup made by a newer Tesria cannot be restored into an older one: it is refused, because the older version would not understand the updated database. See Restoring and undo.