jpmschweitzer/desklock
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

CI: use WATCHTOWER_HTTP_API_TOKEN secret name as set on the repo
Test, Build and Push / test-gateway (push) Successful in 11s
Details
Test, Build and Push / release (push) Skipped
Details
Test, Build and Push / build-gateway (push) Skipped
Details

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
jpmschweitzer
2026-07-14 20:04:29 +02:00
co-authored by Claude Fable 5
parent 79d43ec199
commit 550db5a0ef
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/architecture.md
+1 -1
View File
@@ -257,7 +257,7 @@ Gitea Actions (`.gitea/workflows/build.yml`), following the tatlock/tatlock-ui p
Gitea registry, create a release, and trigger Watchtower to roll the running
container.
- Required repo/org secrets: `REGISTRY_USER`, `REGISTRY_PASSWORD`,
`WATCHTOWER_TOKEN` (same trio tatlock uses).
`WATCHTOWER_HTTP_API_TOKEN` (same trio tatlock uses).
- The gateway is a service in the **`tatlock-ui` Portainer stack**
(`system-admin-toj/containers/stacks/tatlock-ui.yml`, registered in
`CONTAINERS.md`): it shares `docker-dataplane` with Speaches (service-name URL