docs(wiki): migration-based start/update flow and restore (R4) Deployment: the start step now describes versioned migrations (build / baseline / apply) instead of db push, plus the first-start baseline and the stop on a mismatch. Troubleshooting: adopt the restore wording to migrations and add a section for the two deliberate start stops (schema mismatch, failed migration) plus the DB_MIGRATE_SKIP escape. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Deployment v0.14, Troubleshooting v1.24, Configuration v0.21: database backup before schema changes What the backend does at start (backup in data/backups/ before a schema change, DB_BACKUP_KEEP), restoring from such a copy, and the new variable. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Deployment v0.13: the gap while the containers are replaced, restart notice and proxy page (#305) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Deployment v0.12, Configuration v0.17: shorter wording about the sidecar's HTTP API and the remaining image findings Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Deployment v0.11, Troubleshooting v1.20, Configuration v0.16, Development v0.5: the containers run unprivileged (PR 276) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Deployment v0.10: the images (Debian 13 / Alpine), their health status, how OS patches arrive, scanning them Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Deployment v0.9, Configuration v0.15: the sidecar's HTTP API (9800) is no longer published on the host Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Connection Journal v0.4: banning an address; Configuration v0.13 (IP_BANS_DISABLED), Deployment v0.8, Privacy and Hosting v0.5, Troubleshooting v1.18, Administration v0.6, Home v0.14, sidebar entry Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Visitor address behind a reverse proxy: TRUST_PROXY, Settings -> Network Deployment v0.7 (new section, Coolify bullet), Configuration v0.11 (TRUST_PROXY row), Administration v0.3 (Visitor address), Troubleshooting v1.14 (Too many attempts for everybody). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Files page: how to fix the HTTP 413 from a reverse proxy; umlaut names depend on the server (Troubleshooting v1.3, Deployment v0.6) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Query Console: new page for the console and its live events (Query Console v0.1, Home v0.8, Getting Started v0.6, Setup same machine v0.6, Setup remote v0.6, Tips and Pitfalls v0.4, Troubleshooting v1.2, Deployment v0.5) Also corrects what the wiki said about SSH: it is needed not only for event-triggered bot flows but for chat-command triggers, the Files page and icon picker (WebQuery has no file-transfer commands) and, now, the console's live events. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Files page: document FILES_MAX_UPLOAD_MB, reverse-proxy settings for uploads and the Files troubleshooting (Configuration v0.9, Deployment v0.4, Troubleshooting v1.1) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Wiki v0.3: move README detail in, drop the unofficial-source claim Configuration, Deployment, Development and Music Bots now carry the material being moved out of the README: both environment variable tables, the reverse-proxy and Coolify notes, architecture and dev setup, and the music bot chat command reference. Also removes the passage asserting that TeamSpeak's documentation website states the permission order incorrectly. That site turned out to be an unclaimed, auto-generated Mintlify instance rather than anything official, so it isn't worth calling out by implication. The order itself is unchanged and still cited to permissiondoc.txt, which ships with the server.
Wiki v0.2: structure, navigation and the first written pages Adds navigation plus thirteen pages. Fully written: Home, Getting Started, Permissions, Tips and Pitfalls, Users and Roles. The rest are scaffolded with a short orientation so no link leads nowhere. Permissions documents the five tiers, which layer wins, and the skip and negate flags - including that TeamSpeak's own documentation website states the override order incorrectly.