743af0e28b
Now superseded by k3s self-deploy: build → push → kubectl set image performs rolling rollout, so the in-band docker-compose-on-vega upgrade path (docker:vega:* scripts, /api/server-upgrade route, Dockerfile.source-server, docker-compose.vega.yaml, projects-view "Upgrade Server" button) is dead code. The k3s deploy workflow (.forgejo/workflows/self-deploy.yml) and sf-server kustomization under /srv/infra/clusters/default/tenants/hugo/apps/sf-server/ are the only deploy path going forward. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| api | ||
| globals.css | ||
| layout.tsx | ||
| page.tsx | ||