Files
Chronos/deploy/docker/docker-compose.yml
T
Alby96andClaude Opus 5.5 d560b41b81 feat(server): show the Unraid array's free space and check the archive volume before filing uploads
On Unraid the archive is a user share (FUSE shfs), which reports the share's
primary storage, often the cache, while the mover sends the photos to the
array: the admin panel showed the cache's free space (owner review 2, R2).

- New option SpacePath (server.json) / CHRONOS_SPACE_PATH: the admin panel
  shows that folder's volume; empty, or a folder that cannot be measured, falls
  back to the archive's volume (one warning, at start, not per request).
- VolumeSpace measures folders (DriveInfo; the path root on Windows) and reads
  the filesystem type and mount from /proc/self/mountinfo on Linux (longest
  mount point on segment boundaries, octal escapes, optional fields, the top of
  stacked mounts), since DriveFormat calls an shfs share only "fuse". It is an
  injectable service, so tests simulate a full volume; the /data checks use it.
- ArchiveStatsDto keeps FreeBytes/CapacityBytes for the shown volume and gains
  optional trailing members: the write volume's figures (when a space path is
  in use and they differ), the filesystem type and UsesSpacePath.
- Admin panel (dashboard and archive): a tooltip on the storage figures names
  the volume and its filesystem and, on an shfs share without a space path,
  says they are the primary storage and to map the array view to /space; a
  "Write volume" line shows the archive's own volume when it differs.
- Completing an upload, a render upload or a render node's result checks the
  archive volume for its size plus the 64 MiB reserve before the staging copy
  and answers 507 insufficient_storage, the upload still receiving.
- Diagnostics list the archive and space volumes with filesystem and mount.
- Unraid template: optional read-only "Array view" /space (default
  /mnt/user0/Timelapse) and "Space path" CHRONOS_SPACE_PATH=/space; compose and
  the releases README describe the same as an option.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 21:58:27 +01:00

73 lines
3.8 KiB
YAML

# Chronos Server with PostgreSQL 17. Start: docker compose up -d Admin panel: http://<host>:8080/admin
name: chronos
services:
chronos:
# While the organisation on Gitea is private, sign in before pulling: docker login gitea.encke-hake.ts.net
image: gitea.encke-hake.ts.net/balbosoft/chronos-server:latest
restart: unless-stopped
depends_on:
postgres:
condition: service_healthy
# Publishing a port as another host port ("18443:8443")? Set CHRONOS_PUBLIC_HTTPS_PORT (and _HTTP_PORT) below to the
# host port. LAN discovery reaches clients only with "network_mode: host"; on this bridge network clients add the
# server by its address. With host networking drop "ports", give the postgres service
# ports: ["127.0.0.1:5432:5432"] and set CHRONOS_DB_HOST to 127.0.0.1: the name "postgres" no longer resolves there.
ports:
- "8080:8080"
- "8443:8443"
environment:
CHRONOS_ADMIN_USER: admin
CHRONOS_ADMIN_PASSWORD: ${CHRONOS_ADMIN_PASSWORD:?set CHRONOS_ADMIN_PASSWORD in .env}
# postgres (with the CHRONOS_DB_* values below) or a full connection string: Host=…;Database=…;Username=…;Password=…
CHRONOS_DB: postgres
CHRONOS_DB_HOST: postgres
CHRONOS_DB_NAME: chronos
CHRONOS_DB_USER: chronos
CHRONOS_DB_PASSWORD: ${CHRONOS_DB_PASSWORD:?set CHRONOS_DB_PASSWORD in .env}
# auto (self-signed), pem or proxy. Behind a proxy, set CHRONOS_TRUSTED_PROXIES to the proxy's own address (only
# loopback is trusted otherwise). Give a proxy container a fixed one (ipv4_address, on a network with an ipam
# subnet that this service joins too) and let it reach Chronos on that network, not through a published port.
# Never list a subnet or the network's gateway (.1): Docker relays connections to the published ports (IPv6
# clients, the host) from the gateway, and each of them could then choose its client address. For a proxy on the
# host itself, run this service with network_mode: host; the proxy then reaches Chronos over loopback.
CHRONOS_TLS_MODE: auto
# CHRONOS_TRUSTED_PROXIES: "172.30.0.10"
# CHRONOS_PUBLIC_HTTPS_PORT: "8443"
CHRONOS_SERVER_NAME: Chronos Server
# Jobs run one at a time. Photos the running job processes at once (default: half the cores), and the priority queue
# (a higher job pauses the running one, which resumes afterwards). Set here, they can no longer be changed in the
# admin panel's Settings.
# CHRONOS_PARALLELISM: "4"
# CHRONOS_PRIORITY_QUEUE: "true"
# Trace, Debug, Information, Warning or Error
CHRONOS_LOG_LEVEL: Information
# The admin panel shows the archive volume's free space. An Unraid share (/mnt/user/<share>) reports its primary
# storage, often the cache: map the share's array view to /space (volumes below) and show that one instead.
# CHRONOS_SPACE_PATH: /space
PUID: ${PUID:-1000}
PGID: ${PGID:-1000}
TZ: ${TZ:-UTC}
volumes:
# The archive folder should belong to PUID:PGID; an empty or root-owned one is given to them at start (the folder
# only, never its contents).
- ${CHRONOS_ARCHIVE:-./archive}:/archive
# Optional, with CHRONOS_SPACE_PATH above: the same share seen on the array only, to show the array's free space.
# - /mnt/user0/Timelapse:/space:ro
- ${CHRONOS_DATA:-./data}:/data
postgres:
image: postgres:17
restart: unless-stopped
environment:
POSTGRES_DB: chronos
POSTGRES_USER: chronos
POSTGRES_PASSWORD: ${CHRONOS_DB_PASSWORD:?set CHRONOS_DB_PASSWORD in .env}
volumes:
- ${CHRONOS_PGDATA:-./pgdata}:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U chronos -d chronos"]
interval: 10s
timeout: 5s
retries: 10