feat: single setup, mass-pass progress, per-server homes, Desktop shares its library (owner review 5, v1.1.0) (#68)
CI / Build and test (push) Successful in 11m36s
CI / Windows tests and installer (push) Skipped
CI / YAML check (push) Successful in 12s
Release / Build, test and publish (push) Successful in 14m56s
CI / PostgreSQL 16 integration (push) Successful in 10m11s
CI / PostgreSQL 17 integration (push) Successful in 10m15s
CI / Docker image (push) Successful in 45s
Release / Server image (push) Successful in 4m55s

Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
This commit was merged in pull request #68.
This commit is contained in:
Alby96 authored and Alby96 committed 2026-11-15 18:11:43 +01:00
1 parent 988068ee8e
commit 20d64af4a4
793 files changed
+23882 -2096

No files matched your search

+6 -1
View File
@@ -76,7 +76,7 @@ with a message naming the variable, except `CHRONOS_PARALLELISM`, which is held
| Variable | Default | Meaning |
|---|---|---|
| `CHRONOS_DATA_PATH` | `/data` (Windows: `C:\ProgramData\Chronos Server`) | Data folder; read before `server.json`, which lives in it |
| `CHRONOS_DATA_PATH` | `/data` (Chronos Server 1.0 for Windows: `C:\ProgramData\Chronos Server`) | Data folder; read before `server.json`, which lives in it |
| `CHRONOS_ARCHIVE_PATH` | `/archive` (Windows: `C:\ChronosArchive`) | Archive folder |
| `CHRONOS_SPACE_PATH` | unset: the archive's volume | A folder whose volume's free space the admin panel shows (`/space`). One that cannot be measured falls back to the archive's with one warning. Uploads always check the archive's own volume (507 when full) |
| `CHRONOS_VIDEOS_PATH` | unset: copying off (`videos_folder_unset`); compose sets `/videos` | Absolute folder *Copy to videos folder* writes into, outside the archive and the data folder |
@@ -194,6 +194,11 @@ or `verify-full`. Or give a whole connection string in `CHRONOS_DB`.
| Database | The index, users and sign-ins, schedules, job history, audit log | `pg_dump` (below). The index part can also be rebuilt from the archive's sidecars (admin panel › Archive › *Rebuild*), the rest cannot |
| `/data` | Settings, the TLS certificate and key, logs | Copy the folder |
The server's id (since 1.1, the app setting `server.id` in the database, announced to clients as `serverId`) travels
with the database: a restore keeps it, so desktops still know the server; a fresh database makes a new id. Never run
two servers from copies of one database: desktops would take them for one server (they warn when a known id comes
back with another certificate and another name).
Back up (the server stopped, so nothing changes while the dump runs):
```sh