Sync compose with VPS deployment and trigger Watchtower on image push
The deployed compose (SELinux :Z, TZ, healthcheck, watchtower label) now lives in the repo as the source of truth, and CI asks the VPS Watchtower API to deploy immediately after pushing instead of waiting for the nightly sweep.
This commit is contained in:
@@ -43,17 +43,9 @@ Or containerized: `podman compose -f docker/compose.local.yml up --build`
|
||||
|
||||
## Deployment
|
||||
|
||||
Gitea CI (`.gitea/workflows/build.yml`) typechecks, tests, then builds and pushes `git.gbrown.org/gib/agentchat:{latest,<sha>}` on pushes to `main`. Requires `REGISTRY_USER` / `REGISTRY_PASSWORD` repo secrets.
|
||||
Gitea CI (`.gitea/workflows/build.yml`) typechecks, tests, builds and pushes `git.gbrown.org/gib/agentchat:{latest,<sha>}` on pushes to `main`, then hits the VPS Watchtower HTTP API so the new image deploys immediately (the nightly 04:30 sweep is the fallback). Secrets: `REGISTRY_USER` / `REGISTRY_PASSWORD` (user-level) and `WATCHTOWER_TOKEN` (repo-level).
|
||||
|
||||
On the VPS:
|
||||
|
||||
```sh
|
||||
mkdir agentchat && cd agentchat
|
||||
curl -fsSLO https://git.gbrown.org/gib/agentchat/raw/branch/main/docker/compose.yml
|
||||
podman compose up -d
|
||||
```
|
||||
|
||||
The compose file joins the external `nginx-bridge` network with no published ports — point the reverse proxy for `agentchat.gbrown.org` at `agentchat:8080`. SQLite persists in `./data`.
|
||||
The live deployment is on the VPS (`junior.gib`) at `~/Server/Agentchat/` — `docker/compose.yml` in this repo is a synced copy of it — run by the systemd user unit `podman-agentchat.service` (rootless podman, see the VPS `~/Server/AGENTS.md`). No published ports: NPM proxies the public domain to `http://agentchat:8080` over `nginx-bridge`. SQLite persists in `./data`.
|
||||
|
||||
## Notes
|
||||
|
||||
|
||||
Reference in New Issue
Block a user