4 Commits

Include renames

Author	SHA1	Message	Date
claudeandClaude Opus 4.8	c249d6a6e9	Prod: load SMTP env via envFrom secretRef (flat, paste-proof) ... Replace the six nested secretKeyRef env entries with a single 'envFrom: - secretRef: { name: verso-smtp, optional: true }' in both the standalone app manifest and the prod workflow. Avoids the deep nesting that tripped strict server-side decoding, and is simpler to edit. The secret's keys must now be named exactly like the env vars (OVERLEAF_EMAIL_*). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-03 12:40:07 +00:00
claudeandClaude Opus 4.8	2d8f23509a	Prod: standalone Deployment/Service bootstrap files; drop namespace create ... - Add server-ce/k8s/verso-prod-data.yaml (Mongo + Redis) and verso-prod-app.yaml (Verso app), mirroring the workflow so the verso namespace can be bootstrapped/validated by hand. - Drop 'kubectl create namespace verso' from the prod workflow (namespace is pre-created), so the runner only needs namespaced rights in verso, matching the test namespace. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-03 12:03:02 +00:00
claudeandClaude Opus 4.8	0f640c74b2	Prod: provision PVCs out of band (storageClass under operator control) ... - Add server-ce/k8s/verso-prod-pvcs.yaml (mongo-data/redis-data/verso-data, ReadWriteOnce, storageClassName left for the operator to set — use a Ceph RBD block class). - Drop the inline PVC definitions from deploy-verso-prod.yml so it won't fight the operator-provisioned PVCs; the deploy now assumes they already exist. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-03 11:36:41 +00:00
claudeandClaude Opus 4.8	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