diff options
| author | Paul Buetow <paul@buetow.org> | 2026-07-03 23:17:40 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2026-07-03 23:17:40 +0300 |
| commit | 51b8f2849c7ac3f3b135e4ae1fae22ea54efae68 (patch) | |
| tree | ca4285ba0f587ac90b22b496e151773972751a1c | |
| parent | 67babb244b8ab6fcdfe3748b1c52fcac60eb2ed4 (diff) | |
docs: move f3s k3s deployment details to private f3s skill reference
Amp-Thread-ID: https://ampcode.com/threads/T-019f299f-7596-73b6-ba71-0f71fcd3c131
Co-authored-by: Amp <amp@ampcode.com>
| -rw-r--r-- | README.md | 15 | ||||
| -rw-r--r-- | ychat/DOCKER.md | 30 |
2 files changed, 12 insertions, 33 deletions
@@ -118,15 +118,12 @@ podman rm -f ychat ## Deploying to the f3s k3s cluster -This is covered in detail in [`./ychat/DOCKER.md`](ychat/DOCKER.md) (push -steps, Helm chart, ArgoCD Application in the -[`conf` repo](https://codeberg.org/snonux/conf), path -`f3s/ychat/helm-chart`). **The DB-backed build described in this README is -not deployed there yet** — the live LAN URL -(**https://ychat.f3s.lan.buetow.org/**) currently still serves the older, -in-memory-only, no-database image. Rolling out this build needs a persistent -volume for `/app/data` (the existing Helm chart doesn't provision one) and -is a deliberate follow-up, not automatic. +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 not deployed +there yet** — the live LAN URL (**https://ychat.f3s.lan.buetow.org/**) +currently still serves the older, in-memory-only, no-database image. --- diff --git a/ychat/DOCKER.md b/ychat/DOCKER.md index 3bb6dfd..871d167 100644 --- a/ychat/DOCKER.md +++ b/ychat/DOCKER.md @@ -162,34 +162,16 @@ this DB-backed build out is a separate, deliberate decision (needs a persistent volume for `/app/data`, updated Helm chart, etc.) — not done as part of removing the no-DB build option from the codebase. -## Push to the f3s registry +## Deploying to the f3s k3s cluster -```sh -TAG=$(git rev-parse --short HEAD) -podman tag ychat:$TAG r0.lan.buetow.org:30001/ychat:$TAG -podman tag ychat:latest r0.lan.buetow.org:30001/ychat:latest -podman push --tls-verify=false r0.lan.buetow.org:30001/ychat:$TAG -podman push --tls-verify=false r0.lan.buetow.org:30001/ychat:latest -``` - -## Deploy (GitOps) - -Config lives in the `conf` repo (mirrored on the in-cluster git-server): - -- Helm chart: `f3s/ychat/helm-chart` -- ArgoCD app: `f3s/argocd-apps/services/ychat.yaml` - -The Deployment pulls `registry.lan.buetow.org:30001/ychat:<TAG>` (tag matches -`appVersion` in `Chart.yaml`). Logs go to an `emptyDir` on `/app/log` — -ephemeral by design. The SQLite database at `/app/data` needs a real -persistent volume (PVC) to survive pod rescheduling — the current Helm chart -was written for the no-DB build and doesn't provision one yet; see "History" -above. +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 +(`https://ychat.f3s.lan.buetow.org/`) still runs the old no-DB image. ## Optional follow-ups (not in scope for this task) - Port to a modern toolchain (`hash_map`→`unordered_map`, fix implicit returns, modernise `configure.ac`) and drop the legacy-C++ patches. - Fix plaintext password storage/comparison. -- Actually deploy this build to f3s (PVC for `/app/data`, updated Helm - chart, ArgoCD sync) — a human decision, not automated here. |