TAI/TA-Deployment-Broker
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update gui

Browse Source
This commit is contained in:
David Schroeder
2026-07-28 21:11:54 -05:00
parent 6c4ce8f6df
commit 555aae0ab2
12 changed files with 71 additions and 58 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+6 -6
View File
@@ -2,13 +2,13 @@
TAPM Deployment Access is a short-lived authorization broker for protected
deployment packages and installer actions. Technicians authenticate through
the bundled Gitea service, create deployment codes, and authorize a limited
the bundled Git service, create deployment codes, and authorize a limited
number of hosts for selected capabilities.
The production layout is a self-contained, single-VM Docker deployment:
- Go broker with a persistent embedded SQLite database
- rootless Gitea with SQLite, repositories, and package registry
- rootless Git service with SQLite, repositories, and package registry
- Nginx reverse proxy for both public domains
- Certbot and Let's Encrypt HTTP-01 certificate management
- explicit runtime storage under `config/` beside the Compose files
@@ -19,7 +19,7 @@ needs to forward public TCP 80 and 443 to the configured Docker VM ports.
All services are managed by one Compose project while remaining separate
containers for independent health checks and upgrades.
See [docs/deployment.md](docs/deployment.md) for the installation, Gitea setup,
See [docs/deployment.md](docs/deployment.md) for the installation, Git setup,
TLS bootstrap, repository move, renewal, backup, and update procedures. The
ProxMenu integration contract is in [docs/client-api.md](docs/client-api.md).
@@ -32,9 +32,9 @@ After cloning the repository, run:
```
The installer defaults to `SSL_MODE=none`, writes a mode-`0600` `.env`, creates
the runtime directories and Docker network, and starts Gitea behind the
HTTP-only Nginx test configuration. It does not invent Gitea OAuth or package
credentials. After creating those resources in Gitea, run
the runtime directories and Docker network, and starts Git behind the
HTTP-only Nginx test configuration. It does not invent Git OAuth or package
credentials. After creating those resources in Git, run
`./manage.sh configure-broker` and `./manage.sh start`.
New deployment codes default to seven days. While a code is active, the Codes