On Unraid the archive is a user share (FUSE shfs), which reports the share's
primary storage, often the cache, while the mover sends the photos to the
array: the admin panel showed the cache's free space (owner review 2, R2).
- New option SpacePath (server.json) / CHRONOS_SPACE_PATH: the admin panel
shows that folder's volume; empty, or a folder that cannot be measured, falls
back to the archive's volume (one warning, at start, not per request).
- VolumeSpace measures folders (DriveInfo; the path root on Windows) and reads
the filesystem type and mount from /proc/self/mountinfo on Linux (longest
mount point on segment boundaries, octal escapes, optional fields, the top of
stacked mounts), since DriveFormat calls an shfs share only "fuse". It is an
injectable service, so tests simulate a full volume; the /data checks use it.
- ArchiveStatsDto keeps FreeBytes/CapacityBytes for the shown volume and gains
optional trailing members: the write volume's figures (when a space path is
in use and they differ), the filesystem type and UsesSpacePath.
- Admin panel (dashboard and archive): a tooltip on the storage figures names
the volume and its filesystem and, on an shfs share without a space path,
says they are the primary storage and to map the array view to /space; a
"Write volume" line shows the archive's own volume when it differs.
- Completing an upload, a render upload or a render node's result checks the
archive volume for its size plus the 64 MiB reserve before the staging copy
and answers 507 insufficient_storage, the upload still receiving.
- Diagnostics list the archive and space volumes with filesystem and mount.
- Unraid template: optional read-only "Array view" /space (default
/mnt/user0/Timelapse) and "Space path" CHRONOS_SPACE_PATH=/space; compose and
the releases README describe the same as an option.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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>