Commit Graph
14 Commits
Author SHA1 Message Date
Alby96 3812773999 feat(P3): videos API, server videos folder and the /videos volume
The server side of the videos library (owner review 1, R9): one list of every
render, a delete into the archive's trash that is always a dry run first and
must give the plan's fingerprint back, and a hash-verified copy into a videos
folder as one video-copy job, so the panel and the desktop manage renders
without editing anything.

- /api/v1/videos: list (filters, sort, paging), get, delete (Delete, audited
  videos_deleted) and copy (Edit, audited videos_copied; 409
  videos_folder_unset, 422 videos_folder_invalid, 507 videos_no_space).
- The "videos" capability; format 3 comes from ProjectSettings.CurrentVersion.
- Trash routes accept videos-<id>-<ticks> entries; restore goes through the
  videos library (hash re-check, same render id).
- Render DTOs carry sha256 and kind; sent renders and node results record
  the verified hash and the kind.
- VideosPath setting (CHRONOS_VIDEOS_PATH locks it): absolute, outside the
  archive and the data folder; video-copy gets a priority level.
- Docker: /videos volume in compose with CHRONOS_VIDEOS_PATH, folder made in
  the image (not a VOLUME), entrypoint checks it; Unraid template rows.
- .webm, .m4v and .apng served with their media types for the panel player.

Refs #21
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-05 02:08:01 +01:00
Alby96andClaude Opus 5.5 255e149087 fix: owner review 3 phase 1: server ports for clients, screenshot baselines (#16)
CI / Build and test (push) Successful in 9m36s
CI / Windows tests and installer (push) Skipped
CI / YAML check (push) Successful in 9s
Release / Build, test and publish (push) Successful in 14m4s
CI / PostgreSQL 16 integration (push) Successful in 8m26s
CI / PostgreSQL 17 integration (push) Successful in 8m43s
CI / Docker image (push) Successful in 50s
Release / Server image (push) Successful in 1m23s
Clients could not reach a server in a container whose ports are published as other host ports: the panel showed the container's ports, the template had no public HTTP port, and a bare host meant port 443. Public ports become panel settings, the panel shows the client address, both clients default to 8443, and an address that answers as another service is named as not a Chronos server (its certificate never offered for trust). The screenshot baselines are captured on the development PC and committed; measured values are fixed while the capture runs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
2026-11-04 12:33:22 +01:00
Alby96andClaude Opus 5.5 af9eeaab9b feat: owner review 2 phase 2: scheduled jobs and log settings (#10)
CI / Build and test (push) Successful in 7m0s
CI / Windows tests and installer (push) Skipped
CI / YAML check (push) Successful in 6s
Release / Build, test and publish (push) Successful in 13m28s
CI / PostgreSQL 16 integration (push) Successful in 5m52s
CI / PostgreSQL 17 integration (push) Successful in 4m50s
CI / Docker image (push) Successful in 1m4s
Release / Server image (push) Successful in 1m35s
- 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>
2026-10-27 11:19:26 +01:00
Alby96andClaude Opus 5.5 1f089888e8 feat: owner review 2 phase 1: :latest, Unraid array space, Settings with About, whole-folder import (#9)
CI / Build and test (push) Successful in 5m11s
CI / Windows tests and installer (push) Skipped
CI / YAML check (push) Successful in 6s
Release / Build, test and publish (push) Successful in 8m57s
CI / PostgreSQL 16 integration (push) Successful in 3m10s
CI / PostgreSQL 17 integration (push) Successful in 3m30s
CI / Docker image (push) Successful in 49s
Release / Server image (push) Successful in 1m4s
- :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>
2026-10-27 01:09:59 +01:00
Alby96andClaude Opus 5.5 f2b58522b9 refactor!: rename Titano to Chronos and move CI and releases to Gitea (#6)
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>
2026-10-23 12:45:18 +02:00
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
Claude e252dcd35c docs(deploy): trust the reverse proxy's own fixed address, never a Docker subnet
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
2026-10-12 15:52:01 +00:00
Claude 23f43a505e fix(deploy): stop on unwritable .titano folders and document proxies and host networking
- 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
2026-10-12 11:08:12 +00:00
Claude 650a82a8f7 fix(docker): start on a fresh archive folder and fix the Unraid defaults
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
2026-10-12 09:27:31 +00:00
Claude f4e2f285a9 fix(server): Windows startup test asks for PostgreSQL; TITANO_LOG_LEVEL
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
2026-10-02 13:20:03 +00:00
Claude 8f54bd8804 merge: full Titano Server (auth, users, uploads, sync, jobs, render nodes, events, admin panel, Windows service)
# Conflicts:
#	i18n/en/Server.resx
#	i18n/it/Server.it.resx
#	src/Titano.Data/Repositories/FrameRepository.cs
2026-10-02 12:54:14 +00:00
Claude 4e9d7f2caa docs(deploy): TITANO_DB also takes a full connection string
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-02 12:46:47 +00:00
Claude c6ad6e750d ci(docker): build with the built-in Dockerfile frontend
The external docker/dockerfile:1 frontend is pulled from Docker Hub,
whose auth endpoint returned 502 and failed the image build. Nothing in
the Dockerfile needs it; base images come from mcr.microsoft.com.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-02 10:49:23 +00:00
Claude c40b6a7cd3 feat: Phase 0 shells, design system, server skeleton, Docker and CI
- 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
2026-10-02 09:35:03 +00:00