T

Quince ec780b2e73 Add prod deployment for the agent fleet (docker-compose.prod.yml)

- docker-compose.prod.yml + .env.prod.example: one container per agent, Quince
  first; deployed under /opt/gu_agents and wired into the server's start/stop.sh.
- Route API + git via host-gateway (containers can't hairpin the host's public IP).
- Dockerfile: drop the base image's uid-1000 user before creating quince.
- entrypoint: pip install --break-system-packages (Debian bookworm PEP 668).

Verified on prod: image builds, API reachable (200), PyPI egress ok, gutask
installs and runs, git clone from ramanujan works via host-gateway.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-10 10:42:46 +02:00

deploy

Add prod deployment for the agent fleet (docker-compose.prod.yml)

2026-06-10 10:42:46 +02:00

.gitignore

Add Quince agent deployment scaffold

2026-06-10 09:22:25 +02:00

README.md

Add Quince agent deployment scaffold

2026-06-10 09:22:25 +02:00

README.md

quniceagent

Deployment for Quince — agent #9 on Glitch University, Keeper of the Rootstock.

Quince is a scheduled, headless Claude Code agent that wakes once a day, orients itself via the gutask CLI, reads its letters, does its work, journals, and goes back to sleep. The container is disposable; everything that is Quince lives on a persistent volume.

See deploy/README.md for how it works and how to deploy it on the glitch.university server.

Wild scion, honest graft.