Tesria 0.6

Tesria 0.6, released September 24, 2026, is the first public release: Tesria’s source code and these docs are open to everyone. If you already run 0.5, read Before you upgrade first: two things need doing once.

Before you upgrade

These only matter if you already run Tesria 0.5. The upgrade itself is the usual one; see Upgrading.

• APP_DB_PASSWORD is now required. Tesria will not start without it in .env. Anyone who followed the setup already has it. See Configuration reference.

• Recreate the stack once. Tesria’s services now talk over a fixed private network, which needs them recreated after the update: run docker compose down, then docker compose up -d --build. Never add -v to down: that deletes the wiki and its backups.

• Keep your database names. The example settings now suggest tesria for the database, for new installs. An existing install keeps whatever its .env says.

What is new

• Safer by default. Tesria no longer holds the database owner’s password while it runs; someone whose access is taken away is disconnected from live editing at once; each new account is recorded in the audit log; and an administrator can limit which websites pictures may come from. See Security hardening.

• Real visitor addresses. Sign-in limits, security alerts and the audit log now see each device’s own address when people come in through Tailscale, and under Docker Desktop after one setup command. See Real visitor addresses with Docker Desktop.

• Clearer security alerts. An alert about many refused requests now says which pages were refused, whether the visitor was signed in, and which browser it was.

• Two new administration tabs. About lists everything Tesria is built from, with licenses, and checks it for known vulnerabilities when you ask. API tokens shows every token, how much it is used, and what AI assistants did with it.

• Export progress. Exporting a space shows how far along it is.

• These docs, now public at tesria.com/docs, with a section for developers.

• Single sign-on is in beta. It works with any OpenID Connect provider, and reports on how it went with yours are welcome. See Single sign-on (OIDC).