Settings no longer makes a folder an archive on its own: a typed or picked folder without archive.json is made one only after a confirmation naming it, and Settings > Import keeps this PC's archive folder and never creates one. A half-typed path or another PC's drive letter could otherwise get .chronos and sidecars written unasked. The server's structure check creates nothing in a root that lost its archive.json (an unmounted disk's empty mount point) and reports it unavailable; /health re-checks when its last check is over 10 s old, so a fix on the host shows without a dashboard read. The admin board reads the server newest first with Order off, counts Published over the server's total, and a Shift range runs along the lane picked in. Admin sizes keep number and unit together. A sent workspace render whose file left exports/ is no longer listed as missing. Desktop Board cards put their actions under the text while the player is open. Start-up range errors name the CHRONOS_* variable; the deploy guide documents the parallelism clamp and the log rule. Refs #29 #31 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Deploying Chronos
How to install, configure, upgrade and back up the Chronos programs. Written for the person who runs them; the
specification behind each behaviour is docs/BRIEF.md (§14.9 configuration and Docker, §18 installer and updates,
§19.5 images, §19.6 Unraid template).
| Guide | For |
|---|---|
| docker.md | Chronos Server in Docker with Compose: image tags, volumes, every CHRONOS_* variable, ports, TLS, PostgreSQL, upgrades, backup and restore, troubleshooting |
| unraid.md | Chronos Server on Unraid with the template deploy/unraid/chronos.xml and the official PostgreSQL template, including host ports other than 8080/8443 |
| desktop.md | Chronos and Chronos Uploader on Windows: Setup, portable mode, updates, uninstall; Chronos Server on Windows |
The short user guide that ships with every release is deploy/releases-repo/README.md (it becomes the README of a
separate releases repository when RELEASES_REPO is set). It and these guides say the same things; these go further.
The pieces
| Program | Runs on | Talks to |
|---|---|---|
| Chronos (desktop) | Windows 10 21H2+ / 11, x64 | Its own archive and index on the PC; optionally a Chronos Server over HTTPS |
| Chronos Uploader | Windows 10 21H2+ / 11, x64 | A Chronos Server over HTTPS |
| Chronos Server | Docker (linux/amd64), Unraid 6.12+, Windows 10/11/Server 2019+ x64 |
PostgreSQL 16 or 17 (Linux), SQLite or PostgreSQL (Windows); its archive folder |
The archive is the source of truth: photos, sidecars, proxies and renders live in ordinary folders, and the database is an index that can be rebuilt from them (BRIEF §7). Users, sign-ins, schedules, job history and the audit log live only in the database, so back up both (see docker.md › Backup and restore).
Where to get them
| What | Where |
|---|---|
Windows installers, portable zips, the Windows server zip, SHA256SUMS |
Releases of BalboSoft/Chronos on https://gitea.encke-hake.ts.net (or of the releases repository) |
| Server image | gitea.encke-hake.ts.net/balbosoft/chronos-server — :latest, :<version>, :nightly |
Compose file and .env example |
https://gitea.encke-hake.ts.net/BalboSoft/Chronos/raw/branch/main/deploy/docker/docker-compose.yml and …/deploy/docker/.env.example |
| Unraid template | https://gitea.encke-hake.ts.net/BalboSoft/Chronos/raw/branch/main/deploy/unraid/chronos.xml |
While the BalboSoft organisation on Gitea is private, downloads, the update check and image pulls work only for
signed-in accounts: run docker login gitea.encke-hake.ts.net before pulling.
Connecting a client in one paragraph
Open the admin panel (http://<host>:<HTTP port>/admin), go to Settings › Network and TLS and copy the Client
address. Type it in Chronos (Server) and in the Uploader. The first connection shows the server's certificate
Fingerprint; compare it with the one on the same admin page and accept it once. When the container's ports are
published as other host ports, set Public HTTP port and Public HTTPS port first, so the client address names the
ports clients can reach (docker.md › Ports).