mi/werkator
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

renaming from gitTally to Werkator

Browse Source
This commit is contained in:
mhoennig
2026-08-30 18:35:49 +02:00
parent 4d76744721
commit 7f550689dd
169 changed files with 1361 additions and 7504 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/adrs/0005-2026-07-07.managed-nginx-tls.md
+9 -9
View File
@@ -6,7 +6,7 @@
- rejected: -
- superseded: -
**Decision [accepted]:** GitTally optionally manages an nginx+certbot Docker container for hosts without a usable reverse proxy — revises the "no managed nginx" part of ADR 0004; deployment behind an existing reverse proxy stays the default.
**Decision [accepted]:** werkator optionally manages an nginx+certbot Docker container for hosts without a usable reverse proxy — revises the "no managed nginx" part of ADR 0004; deployment behind an existing reverse proxy stays the default.
## Context and Problem Statement
@@ -15,22 +15,22 @@ That decision was carried over from the rewrite plan without validating it again
### Technical Background
GitTally must run on Hostsharing managed container environments.
These hosts provide Docker but no root access and no host web server that GitTally could sit behind.
Without the managed nginx container, GitTally cannot be served over HTTPS there at all.
werkator must run on Hostsharing managed container environments.
These hosts provide Docker but no root access and no host web server that werkator could sit behind.
Without the managed nginx container, werkator cannot be served over HTTPS there at all.
The legacy script already solved this: it wrote an nginx config, ran an nginx Docker container, and obtained/renewed Let's Encrypt certificates via a certbot container in webroot mode.
## Considered Options
* Keep ADR 0004 as is (host reverse proxy only)
* Re-add the legacy managed nginx+certbot container as an opt-in feature
* External tooling (user-maintained compose stack next to GitTally)
* External tooling (user-maintained compose stack next to werkator)
### Host reverse proxy only
#### Advantages
- No container lifecycle or certificate code in GitTally.
- No container lifecycle or certificate code in werkator.
#### Disadvantages
@@ -38,7 +38,7 @@ The legacy script already solved this: it wrote an nginx config, ran an nginx Do
### Opt-in managed nginx+certbot container
GitTally starts and supervises a labelled nginx container and handles certificate issuance/renewal via certbot, only when explicitly enabled in the config.
werkator starts and supervises a labelled nginx container and handles certificate issuance/renewal via certbot, only when explicitly enabled in the config.
#### Advantages
@@ -48,13 +48,13 @@ GitTally starts and supervises a labelled nginx container and handles certificat
#### Disadvantages
- Re-adds container lifecycle and certificate renewal complexity to GitTally.
- Re-adds container lifecycle and certificate renewal complexity to werkator.
### External compose stack
#### Advantages
- Keeps GitTally itself simple.
- Keeps werkator itself simple.
#### Disadvantages