diff options
| -rw-r--r-- | README.md | 7 | ||||
| -rw-r--r-- | ychat/DOCKER.md | 5 |
2 files changed, 5 insertions, 7 deletions
@@ -118,10 +118,9 @@ podman rm -f ychat ## Deploying to the f3s k3s cluster -Deploying ychat to the f3s homelab k3s cluster (image build/push, Helm chart, -ArgoCD Application, PVC requirements) is **not** documented here — it lives in -the private `f3s` skill reference, since it depends on homelab-specific -infrastructure. **The DB-backed build described in this README is now +Deploying ychat to a homelab k3s cluster (image build/push, Helm chart, +ArgoCD Application, PVC requirements) is homelab-specific and **not** +documented in this public repo. **The DB-backed build described in this README is now deployed** — the live LAN URL (**https://ychat.f3s.lan.buetow.org/**) serves image tag `67babb2` with a persistent volume (`ychat-data-pvc`, hostPath-backed NFS share) mounted at `/app/data`, so registered accounts survive pod diff --git a/ychat/DOCKER.md b/ychat/DOCKER.md index 871d167..cff284c 100644 --- a/ychat/DOCKER.md +++ b/ychat/DOCKER.md @@ -165,9 +165,8 @@ part of removing the no-DB build option from the codebase. ## Deploying to the f3s k3s cluster Homelab-specific deployment (image push to the private registry, Helm chart, -ArgoCD Application, PVC for `/app/data`) is **not** documented here — it lives -in the private `f3s` skill reference, since it depends on homelab -infrastructure. It is **not yet deployed**: the live cluster +ArgoCD Application, PVC for `/app/data`) is homelab-specific and **not** +documented in this public repo. It is **not yet deployed**: the live cluster (`https://ychat.f3s.lan.buetow.org/`) still runs the old no-DB image. ## Optional follow-ups (not in scope for this task) |