Development Site
Overview
| Field | Value |
|---|---|
| Purpose | Serve development/static deployment content |
| Owner | Development team; named owner to be recorded |
| Criticality | Low |
| Image | nginx:stable-alpine-slim |
Architecture
The restored Forgejo Actions runner publishes build artifacts under the
rootless runner data volume on CT 101.
Installation
The container is labeled to Compose project /root/kh3-dev-site, but the June 9 Compose-file scan did not find a deployment file there. Verify whether the gitea stack owns it.
Configuration
- Actions publish path:
/opt/podman/volumes/forgejo/runner-data/publish/kh3-dev-site - Image cache path:
/opt/podman/volumes/forgejo/runner-data/cache/kh3-dev-site-images - Network:
aproxy - Restart policy:
always - Route: To be verified
Operational Procedures
docker logs --tail=100 kh3-dev-site
docker inspect kh3-dev-site
docker restart kh3-dev-site
Coordinate changes with Forgejo Actions because the runner writes to the rootless runner artifact directory. A separate serving/sync step is still needed before treating this as the public site root.
Troubleshooting
Check the most recent Actions deployment, file ownership, Nginx logs, and Traefik route.