# Chronos Server with PostgreSQL 17. Start: docker compose up -d Admin panel: http://: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 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 - ${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