gamertan
b2cc4482f6
Publish the reviewed version identity fix and mark preview 1 withdrawn.\n\nPrivate-Source-Commit: 9907afdfa18099ac488fe4011291ea454036435a\nPrivate-Source-Tree: 3a5e666dd6a0c69a07f7804612c8e3dc3474966a\nHimesan-Output-Permission: v1.0\nAI-Assistance: OpenAI Codex assisted implementation and review. Signed-off-by: Cole Speelman <crspeelman@gmail.com>
1.7 KiB
Gamertan Tend
Tend is an opinionated release and deployment tool for small Go services on Linux, systemd, and Caddy. It packages a clean pushed commit, records exact build provenance, activates a health-checked candidate, and keeps rollback state explicit.
The first preview deliberately supports two quiet deployment shapes:
- Caddy-switched blue/green services.
- A singleton service with an isolated transient candidate check.
It does not manage databases, migrations, containers, Kubernetes, or arbitrary shell hooks. Application-specific data activation remains application-specific.
Commands
tend check --config tend.json
tend package --config tend.json --version v0.1.0-preview.2 --out dist
tend deploy --config /etc/example/tend.json --artifact FILE --sha256 HEX --approve-sha256 HEX
tend status --config /etc/example/tend.json
tend rollback --config /etc/example/tend.json
tend prune --config /etc/example/tend.json --keep 3 [--apply]
deploy, rollback, and applied pruning are target-host operations. Transfer
credentials and production configuration stay outside source repositories.
Dry-run and digest approval are intentional friction.
The first public preview has completed maintenance releases and explicit rollback/reactivation for both Gamertan and the Sandwich Hime website using one reviewed Tend candidate. See the dated dogfood evidence for exact scope and limitations. The canonical public repository begins with a sanitized root snapshot rather than the private development history.
Licensing
Tend and its release machinery are AGPL-3.0-only. Reusable example
configuration and service templates under examples/ are 0BSD.