Commit Graph
3 Commits
Author SHA1 Message Date
Alby96andClaude Opus 5.5 f30eb2904a fix: address the owner review 5 review
Setup: a kept 1.0 Uploader no longer fixes the scope and folder, the
Remove tooltip promises kept files only with a hashed log, and a
single-program setup preselects it. The Uploader always downloads the
setup. Sync links move to the server id at every sign-in while folders
wait for jobs and open editors; jobs of a pending homes sort still find
their projects. A shared library exposes only the shared archive's
client-visible jobs and events, render nodes take only client renders,
and the share counts as its own while starting. Progress: a new step
waits a quarter interval and a trailing timer publishes the last state;
the job bar tooltip carries the whole line; Recent maintenance and the
Server jobs list pick up jobs that start while they are shown.

Refs #64 #65 #66 #67

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 16:19:56 +01:00
Alby96andClaude Opus 5.5 7d0c6554a4 feat(setup): one setup for Chronos Desktop and Chronos Uploader
Chronos Server now ships as a Docker image only, so the Windows setup no
longer offers it and the separate Uploader setup goes: one setup installs,
updates, adds and removes Chronos Desktop and Chronos Uploader in place.

- Install log format 2 records each component's files, shortcuts, version
  and SHA-256; format 1 logs (1.0) are still read. A file of a removed
  program that changed since setup installed it is kept, never deleted.
- A Chronos Server 1.0 for Windows installed by 1.0 is retained as "no
  longer offered": its files and service are untouched until the user
  unticks it or explicit /COMPONENTS leave it out; then it is removed with
  its service. A format 1 log keeps every file the payload does not know.
- The separate 1.0 Chronos Uploader product is replaced: the Uploader is
  preselected, its sign-in entry moves to the new copy (Task Manager state
  kept), its shortcut is handed over and the old product is uninstalled.
  An all-users copy under a per-user install stays and is said so.
- The setup window shows the dry-run plan (Changes: adds, removes,
  replaces) before Update; with every program unticked the primary action
  becomes Uninstall. /COMPONENTS=Desktop names the desktop app.
- pack-installer refuses Server (--legacy packs a 1.0 one for the CI test);
  release.yml publishes only Chronos-Setup-<v>.exe and the portable zip;
  the installer test covers add/remove in place, the Uploader replacement
  and the retained Server.

Refs #64

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 13:13:54 +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