claude 54ccb3d712 Add prod deploy workflow (verso namespace, persistent, friends-only) ...

New .gitea/workflows/deploy-verso-prod.yml triggered by pushes to the 'prod'
branch — a real production target distinct from the ephemeral test rig:

- Runs in the 'verso' namespace; Mongo/Redis/app-data on PersistentVolumeClaims,
  applied idempotently and NEVER deleted (data survives deploys).
- Replica set initialised only once; admin created only if no users exist.
- Builds/pushes verso:stable (separate tag from test's verso:latest);
  imagePullPolicy Always so each rollout pulls the new build.
- SMTP via an optional 'verso-smtp' Secret (no credentials in the repo);
  anonymous read-write sharing left off and public registration off
  (friends-only).
- Example Ingress for verso.alocoq.fr at server-ce/k8s/verso-prod-ingress.example.yaml
  (apply by hand to match the existing TLS/annotation setup).

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

2026-06-03 11:21:33 +00:00

..

deploy-verso-prod.yml

Add prod deploy workflow (verso namespace, persistent, friends-only)

2026-06-03 11:21:33 +00:00

deploy-verso.yml

README logo + dates; capitalize Alpha in instance title

2026-06-03 11:01:23 +00:00