Review fixes on top of the public ports change (owner review 3):
- Settings > Network and TLS: opened over HTTPS, the client address uses the port
the page came through (a container's 8443 published as 8444 with Public HTTPS
port still empty showed the wrong 8443), and a "Use <port>" button fills that
port in. Saving a Public HTTPS port other than the page's asks first, since the
HTTPS redirect follows it at once and a typo would lock the panel's link out.
- GetInfoAsync tells Chronos from other services by stricter rules on both the
trusted and the untrusted-certificate path: any redirect, any answer that is not
JSON, more than 1 MB, or an error without the X-Chronos-Api header is not
Chronos. Another service's certificate is no longer offered for trust after a
cross-scheme redirect, an error page or a JSON 401/403/404, and a JSON 401 over
HTTP no longer reads as a wrong password.
- The HTTP port typed without a scheme (TLS to a plain HTTP port) now gives the
not-Chronos error instead of "the server did not answer".
- The Uploader's certificate question names the address with its port.
- A link-local IPv6 address with a zone index is refused instead of losing it.
- In a container, the first save of the settings removes HttpPort/HttpsPort from
server.json, so the start-up warning stops; the warning says so.
- Guide, README, compose and template: with network type Host the mappings do
nothing and CHRONOS_HTTP_PORT / CHRONOS_HTTPS_PORT move the listening ports off
ones another service uses; the template overview is back to two sentences.
- BRIEF, DECISIONS and CHANGELOG updated; en/it strings added.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The owner's Uploader could not connect: the panel showed the container's
listening ports (8080/8443) as if clients used them, the public ports were
only environment variables (CHRONOS_PUBLIC_HTTP_PORT not even in the Unraid
template), and the clients mapped a bare host to 443, where another service
answered.
- Public HTTP/HTTPS ports are settings (server.json, or locked by
CHRONOS_PUBLIC_*) and apply at once; ServerSettingsDto gains appended
PublicHttpPort, PublicHttpsPort and InContainer members.
- In a container the listening ports are fixed by the template: locked in the
panel, and saved values from earlier versions are ignored with a warning.
- Settings > Network and TLS shows the client address with a Copy button; the
discovery tooltip says a container needs network type Host.
- ChronosAddress (shared by Chronos and the Uploader): no scheme and no port is
https on 8443, https:// keeps 443, a typed port is kept, IPv6 is bracketed.
- GetInfoAsync throws NotChronosServerException for answers that are not a
Chronos server; another service's certificate is never offered for trust
and no credentials are sent to it. Both clients name the address asked.
- Unraid template, compose file, user guide, README, BRIEF, DECISIONS,
CHANGELOG (with an Unraid upgrade note) and ARCHITECTURE updated; en/it
strings added.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Jobs > Scheduled on the desktop and the admin panel. Every timer that queued work is now a visible system schedule: archive scan, upload clean-up, index backup, job-history and audit clean-ups, desktop housekeeping. New actions: verify, thumbnails, proxies, analysis, maintenance, backup, clean-ups, reports.
- The scheduler: migration 0007, in-house recurrence, compare-and-set claim, catch-up, scan at start.
- Log settings: levels, retention, size parts, total limit, daily or hourly rotation, audit retention, diagnostics share; the server writes Debug/Trace to its files again; logging never fails a job.
Upgrade: CHRONOS_LOG_LEVEL set in an existing container locks both levels; migration 0007 is one-way.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
- :latest follows the highest stable release, or the highest pre-release while none is stable (Chronos.Tools release-channels); bad tags are refused before anything is built.
- Unraid: CHRONOS_SPACE_PATH and the template's Array view show the array's free space; the write volume (cache) is shown apart; completions check the archive volume (507).
- Settings is a gear, docked at the foot of the admin sidebar; About is the last part of Settings on the desktop and the panel.
- Import > Folder > Whole folder: one sequence per format (desktop only).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
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>
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>
The compose comments, the releases README and the Unraid template told
users to list the Docker network's subnet (172.17.0.0/16 on Unraid) in
TITANO_TRUSTED_PROXIES. That range holds the gateway, from which Docker
relays IPv6 clients and the host's own connections to published ports,
and on the default bridge every other container: each could again pick
its X-Forwarded-For and X-Forwarded-Proto. The guidance now names the
proxy container's fixed address on a shared user-defined network, warns
against subnets, the gateway and the default bridge, and sends a proxy
on the Docker host to network_mode: host (loopback). The server's
parse error no longer suggests a /12 network.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
- Entrypoint: an existing .titano folder or subfolder that PUID:PGID cannot
write stops the container with a one-line error instead of a restart loop;
it is never chowned.
- Compose and README: with network_mode host, publish PostgreSQL on loopback
and set TITANO_DB_HOST to 127.0.0.1; behind a proxy, list it in
TITANO_TRUSTED_PROXIES (loopback only by default). Unraid template gains a
Trusted proxies variable.
- README: what the Windows server requires of its data folder and archive.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
A bind source Docker creates on demand (the compose default, a new
TITANO_ARCHIVE, the image's anonymous volume) is root-owned, so the server,
running as PUID:PGID, crash-looped with a stack trace (DOCKER-2). The
entrypoint now gives an archive mount root that user cannot write to
PUID:PGID when it is empty or owned by root (the folder only, never its
contents), and otherwise exits with a one-line error; it creates and owns
TITANO_DATA_PATH instead of a hard-coded /data (DEPLOY-1), and --help and
--healthcheck touch neither folder. The runtime image empties
ASPNETCORE_HTTP_PORTS, so Kestrel no longer warns "Overriding address(es)"
at every start (DOCKER-6).
Unraid template: the database host defaults to empty and required, since
container names do not resolve on the default bridge (SRS-08, DOCKER-3); a
Public HTTPS port variable goes with a remapped HTTPS port (DOCKER-4); the
time zone description no longer claims logs use it (DOCKER-8). Compose,
.env.example and the public README document the archive folder's owner,
public ports, trusted proxies, that LAN discovery needs host networking
(DOCKER-5), the Unraid database host, and that the Windows service
registers only from Program Files (SRS-06).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
The connection-string test built options with the platform default,
which is SQLite on Windows, so it parsed a file path as a PostgreSQL
connection string. The server gains a log level setting
(TITANO_LOG_LEVEL, also in compose and the Unraid template); the test
servers log warnings only, which cuts the suite's output from 511 to 80
lines so failures stay findable in CI logs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
- Titano.Ui: DESIGN.md tokens (dark/light), generated 16-px icon set,
styles for all standard controls, custom chrome window with snap
layouts, rail, job bar, Auto/manual slider, chips, toasts.
- Titano desktop shell with sections, Settings (language, theme),
About and a --capture screenshot mode.
- Titano Server skeleton: env/server.json configuration, self-signed
TLS with fingerprint, /health, /server/info, i18n endpoint and the
embedded admin panel; in-process server tests.
- Docker image (multi-arch, PUID/PGID, health check), compose file,
Unraid template; CI, release and nightly workflows; changelog tool.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC