renaming from gitTally to Werkator

2026-08-30 18:35:49 +02:00
parent 4d76744721
commit 7f550689dd
169 changed files with 1361 additions and 7504 deletions
@@ -10,7 +10,7 @@

 ## Context and Problem Statement

-The rewrite of `legacy/gitTally` (bash) as a Kotlin/Spring application (see `docs/plan/`) required several cross-cutting architecture decisions.
+The rewrite of `legacy/werkator` (bash) as a Kotlin/Spring application (see `docs/plan/`) required several cross-cutting architecture decisions.
 They were proposed in `docs/plan/README.md`, validated step by step during implementation, and are summarized here as one record.

 ### Technical Background
@@ -26,7 +26,7 @@ Its two structural defects — build status not observable during a build, and a

 ### Persistence: JSON files behind `BuildResultRepository`

-Build results are persisted as a JSON file under `.git/gittally/`, accessed only through the `BuildResultRepository` interface.
+Build results are persisted as a JSON file under `.git/werkator/`, accessed only through the `BuildResultRepository` interface.

 #### Advantages

@@ -54,7 +54,7 @@ Pages render the full state server-side; one hand-written JavaScript file polls

 ### Deployment: no managed nginx, systemd user unit instead

-nginx/Let's Encrypt container management was not ported; `init --systemd` generates a user unit running `java -jar gittally.jar server`, and `docs/deployment.md` documents the reverse-proxy setup with the host's certbot.
+nginx/Let's Encrypt container management was not ported; `init --systemd` generates a user unit running `java -jar werkator.jar server`, and `docs/deployment.md` documents the reverse-proxy setup with the host's certbot.

 #### Advantages

@@ -64,7 +64,7 @@ nginx/Let's Encrypt container management was not ported; `init --systemd` genera

 #### Disadvantages

- HTTPS setup is a manual, host-specific step outside GitTally's control.
+- HTTPS setup is a manual, host-specific step outside werkator's control.

 ## Decision Outcome