Files
Chronos/deploy/docker/docker-compose.yml
T
Alby96andClaude Opus 5.5 43b6871cdc feat: jobs run one at a time, parallelism per photo and a priority queue
Owner review 1, phase 2 (docs/requests/2026-10-15-owner-review-1.md, R2).

Jobs now run one at a time on the desktop and on the server. Parallelism
(Settings > Rendering, TITANO_PARALLELISM) is how many photos the running
job processes at once: thumbnail and proxy passes draw that many photos
together and still write the pack and checkpoints in frame order, decode
tiers are probed that many at a time, the deep analysis measures that many
frames and a render decodes that many ahead. Wherever originals are
developed whole (TIFF, PNG, RAW without a usable preview), fewer run at
once within the memory budget, which the running job now has whole; the
server's frame window is sized to the host instead of 1 GiB.

A new job waits its turn and pausing the running job starts the next one.
An optional priority queue gives each job kind a level (renders, imports
and downloads high, verifies and proxies low by default): a queued job of
a higher level pauses the running one without asking, and that job goes
back to the queue with its checkpoint and resumes by itself afterwards.
Jobs of the same level, and a job's own follow-ups, never interrupt it.
The Jobs screen and the admin panel show the parallelism and the queue;
Settings > Rendering and the admin panel's Settings set them, at once.

TITANO_WORKERS and the Workers key of server.json still set the
parallelism (1 to 64, with a warning at start for the variable).
Titano.Tools gains i18n prune, which removed the renamed keys from the 36
machine-translated languages; the new strings are translated in all 38.

Found while testing: uploads and imports failed when a pass read the
sidecar while they wrote it (atomic writes now retry the rename while a
reader holds the file, and never for a read-only one), and taking a lease
just released while another process read it failed on Windows (the create
now waits for the reader). Five adversarial review rounds checked the
phase before this commit.

Also updates BRIEF (12.8, 14.6, 14.8, 14.9, 24), DECISIONS, CHANGELOG,
ARCHITECTURE, STATUS, the request file and the compose/Unraid templates.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 14:56:24 +02:00

67 lines
3.2 KiB
YAML

# Titano Server with PostgreSQL 17. Start: docker compose up -d Admin panel: http://<host>:8080/admin
name: titano
services:
titano:
image: ghcr.io/alby96/titano-server:latest
restart: unless-stopped
depends_on:
postgres:
condition: service_healthy
# Publishing a port as another host port ("18443:8443")? Set TITANO_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 TITANO_DB_HOST to 127.0.0.1: the name "postgres" no longer resolves there.
ports:
- "8080:8080"
- "8443:8443"
environment:
TITANO_ADMIN_USER: admin
TITANO_ADMIN_PASSWORD: ${TITANO_ADMIN_PASSWORD:?set TITANO_ADMIN_PASSWORD in .env}
# postgres (with the TITANO_DB_* values below) or a full connection string: Host=…;Database=…;Username=…;Password=…
TITANO_DB: postgres
TITANO_DB_HOST: postgres
TITANO_DB_NAME: titano
TITANO_DB_USER: titano
TITANO_DB_PASSWORD: ${TITANO_DB_PASSWORD:?set TITANO_DB_PASSWORD in .env}
# auto (self-signed), pem or proxy. Behind a proxy, set TITANO_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 Titano 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 Titano over loopback.
TITANO_TLS_MODE: auto
# TITANO_TRUSTED_PROXIES: "172.30.0.10"
# TITANO_PUBLIC_HTTPS_PORT: "8443"
TITANO_SERVER_NAME: Titano 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.
# TITANO_PARALLELISM: "4"
# TITANO_PRIORITY_QUEUE: "true"
# Trace, Debug, Information, Warning or Error
TITANO_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).
- ${TITANO_ARCHIVE:-./archive}:/archive
- ${TITANO_DATA:-./data}:/data
postgres:
image: postgres:17
restart: unless-stopped
environment:
POSTGRES_DB: titano
POSTGRES_USER: titano
POSTGRES_PASSWORD: ${TITANO_DB_PASSWORD:?set TITANO_DB_PASSWORD in .env}
volumes:
- ${TITANO_PGDATA:-./pgdata}:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U titano -d titano"]
interval: 10s
timeout: 5s
retries: 10