Owner review 2, R11 asked for more log settings. The file sink now writes daily or hourly files, continues a full file in numbered parts and prunes by age and by the total size (never the file being written); its options change while it runs. Server: the file and console levels are separate and read by the logging filters at every line, so the admin panel's new Logs group applies without a restart; the engine's level follows the lower of the two. This also fixes a bug: the file logger was fixed at Information, so CHRONOS_LOG_LEVEL=Debug or Trace never reached the files. New variables CHRONOS_LOG_CONSOLE_LEVEL, CHRONOS_LOG_RETENTION_DAYS, CHRONOS_LOG_MAX_FILE_MB, CHRONOS_LOG_MAX_TOTAL_MB, CHRONOS_LOG_ROTATION, CHRONOS_AUDIT_RETENTION_DAYS and CHRONOS_DIAGNOSTICS_LOG_MB lock their settings like the others; the diagnostics zip keeps the configured share of each log. Desktop: Settings > Advanced gains Log level, Keep logs, File size, Logs total, Rotation and Diagnostics logs, applied at every save; Advanced's Reset section restores them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit cc875784e4952ee0e4c807b9d9c18496d3d5a8c3)
86 lines
4.7 KiB
YAML
86 lines
4.7 KiB
YAML
# Chronos Server with PostgreSQL 17. Start: docker compose up -d Admin panel: http://<host>:8080/admin
|
||
name: chronos
|
||
|
||
services:
|
||
chronos:
|
||
# :latest is the newest stable release (before the first one, the newest pre-release); :<version> pins a release;
|
||
# :nightly is the development version rebuilt every night, not for production.
|
||
# 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"
|
||
# The log files' and the console's level: Trace, Debug, Information, Warning, Error, Critical or None
|
||
CHRONOS_LOG_LEVEL: Information
|
||
# The log files (/data/logs) and the audit log: the console's own level, the days files are kept, the size (MB) at
|
||
# which a file continues in a numbered one and that of all files (the oldest go beyond it; 0: no limit for either),
|
||
# daily or hourly files, the days audit entries are kept (0: forever) and the MB of each log in the diagnostics zip.
|
||
# Set here, they can no longer be changed in the admin panel's Settings › Logs.
|
||
# CHRONOS_LOG_CONSOLE_LEVEL: Warning
|
||
# CHRONOS_LOG_RETENTION_DAYS: "14"
|
||
# CHRONOS_LOG_MAX_FILE_MB: "50"
|
||
# CHRONOS_LOG_MAX_TOTAL_MB: "1024"
|
||
# CHRONOS_LOG_ROTATION: daily
|
||
# CHRONOS_AUDIT_RETENTION_DAYS: "0"
|
||
# CHRONOS_DIAGNOSTICS_LOG_MB: "4"
|
||
# 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
|