CI / Build and test (push) Successful in 8m14s
CI / Windows tests and installer (push) Skipped
CI / YAML check (push) Successful in 7s
Release / Build, test and publish (push) Successful in 13m19s
CI / PostgreSQL 16 integration (push) Successful in 4m49s
CI / PostgreSQL 17 integration (push) Successful in 5m28s
CI / Docker image (push) Successful in 53s
Release / Server image (push) Failing after 10s
The owner renamed the product and moved the repository to the self-hosted Gitea (https://gitea.encke-hake.ts.net/BalboSoft/Chronos) for more control, and asked for Actions and a first automatic release with the server package and the Windows exe (docs/requests/2026-10-23-chronos-gitea.md). - Chronos everywhere: a byte-exact rename of contents and paths, then a per-language review of the forms the old name's ending had dictated. - Gitea instead of GitHub: the update check, licence, issue and support links read ChronosReleasesUrl; the update check takes the highest stable version, offers a pre-release build its final release and reports a repository it cannot see as a failed check. EULA, security policy and Gitea issue forms live at the repository root. - Gitea Actions for the Linux act_runner (.gitea/workflows): CI, release, nightly image and performance gates in the .NET SDK container with git checkout and the system SQLite. The release cross-compiles the Windows programs, checks their icon, version and DPI manifest, packs installers and zips, publishes the Gitea release and pushes the server image (REGISTRY_TOKEN). Windows-only tests run in an opt-in job on a Windows runner (WINDOWS_RUNNER). - New Chronos.Tools commands: zip, gitea-release, postgres-ci (replaces the docker-exec script, which Gitea's service containers do not allow; the throw-away server runs without durability) and pe-check. - Timed tests take their budget from TestTiming (CHRONOS_TEST_TIME_FACTOR, 3 on the shared runner; the weekly performance gates keep theirs). BREAKING CHANGE: programs, settings, data folders, file types, environment variables and the Docker image use the new name; nothing is migrated from Titano, which never had a release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
68 lines
3.4 KiB
YAML
68 lines
3.4 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
|
|
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
|