Uninstalling and moving
How to stop Tesria, move it, or remove it. Stopping keeps everything; moving takes the wiki with it; removing deletes it. Each is below, in that order, from the gentlest to the one that cannot be undone.
Stopping
docker compose downStops and removes the containers. Your data stays in its volumes, and docker compose up -d brings everything back as it was.
Moving one space
A wiki pack carries one space, with its pages, history, comments and attachments, to another Tesria. Export it with Prepare the Pack under Export as a Pack in the space’s settings, then import it on the other Tesria with Import a Pack on the Spaces page. See Wiki packs.
Moving the Tesria folder
On the same computer, to another place: stop Tesria with docker compose down, move the whole folder, including the hidden file .tesria-install in it, and run docker compose up -d in its new place. That file is how Tesria knows the folder is its own.
If you unzipped a fresh copy somewhere else instead, copy your .env into it, and tell Tesria the new folder is now its own before starting it there. The old folder then no longer starts it:
docker compose run --rm init use-this-folder
docker compose up -dMoving the whole Tesria
To a new computer, taking everything: every space, account and setting. It moves the newest backup across and restores it.
Step 1: Take a backup on the old computer
Choose Admin, Backups, Back Up Now, and wait until it finishes.
Step 2: Pack up the backups
In the Tesria folder on the old computer, list the backups and note the name of the newest db-<time>.dump: it is the one you restore in step 4.
docker compose exec backup ls /backupsThen pack them all into one file and copy it out of the backup service, into the Tesria folder:
docker compose exec backup tar czf /tmp/tesria-backups.tgz -C /backups .
docker compose cp backup:/tmp/tesria-backups.tgz tesria-backups.tgz
docker compose exec backup rm /tmp/tesria-backups.tgzThe same commands work in Windows PowerShell. That makes tesria-backups.tgz. Copy it to the new computer, into its Tesria folder.
Step 3: Install Tesria on the new computer
As in Quick start, with the same DOMAIN in its .env to keep the same address. Start it with docker compose pull and docker compose up -d, wait until app is healthy, and skip the setup wizard.
Step 4: Restore the backup
docker compose cp tesria-backups.tgz backup:/tmp/
docker compose exec backup tar xzf /tmp/tesria-backups.tgz -C /backups
docker compose exec backup ls /backupsThen restore the dump you noted in step 2, by its name, and restart Tesria:
docker compose exec backup /scripts/restore.sh db-<time>.dump
docker compose restart app
docker compose restart collabNot the newest dump in the list. The new computer backed itself up when it first started, so the newest db-<time>.dump in the list is its own empty wiki. Restoring it by name restores nothing you want. Run without a name, restore.sh passes over it and restores the newest dump that holds accounts.
Step 5: Point people at the new computer
If you use a domain, point it at the new server. If people use the local certificate, each device trusts the new one: see Trusting the local certificate. Then set up the offsite copies again, as in Offsite copies.
Removing Tesria completely
This deletes the wiki and every backup on this computer. It cannot be undone. First take a copy you can restore from somewhere else, or be sure you never want it again.
First make sure this folder is the Tesria you mean to remove. With more than one Tesria folder on a computer, a folder that was never given its own name is the other Tesria, and removing it here deletes that wiki. In the Tesria folder:
docker compose run --rm init check-folderGo on only if it says this folder is the one Tesria was installed from. If it says it is not, stop: see A second Tesria on the same computer in Installing with Docker Compose. Then:
docker compose down -v --rmi local-v deletes the volumes, which hold the database, the attachments, the backups, and the generated passwords and keys that open the database and the backups. --rmi local deletes the images built for Tesria. Offsite copies are not touched: delete those from your cloud storage, network drive or removable drive yourself. Then you can delete the Tesria folder.
Applies to | Tesria 0.5 and later |
|---|---|
Updated | October 2, 2026 |
Changes | Revised. |