67b07634ae
- app/: Emdash scaffold (Astro 6, node target) with cmses/plugins/pages collections - app/seed/seed.json: WordPress→Emdash parity for kotkanagrilli.fi (~30 entries) - Dockerfile + docker/entrypoint.sh: multi-stage build, single PVC at /app/state - deploy/helm/: chart mirroring emdash-kotkanagrilli (single-replica, sqlite, kotkan) - deploy/fleet-overlay/: HelmRelease/source/image-automation templates for anton-helm-workloads (staging + production) - .woodpecker/container.yaml: arm64 build, three OCI tags per push (immutable 0.1.<pipeline> + floating <branch> + <branch>-latest) - .ddev/: local dev with nginx proxy to emdash on :4321 - README/DEPLOYMENT/ARCHITECTURE/CLAUDE: docs covering the three-repo pipeline (cms-plugins + anton-helm-workloads + Gitea OCI registry)
15 lines
570 B
Markdown
15 lines
570 B
Markdown
# deploy/
|
|
|
|
Two sibling directories with very different lifecycles:
|
|
|
|
- **`helm/`** — the Helm chart that runs the pod. FluxCD pulls it
|
|
directly from this repo on the branch matching each environment
|
|
(no `helm push` step). Edit this in lockstep with the app code that
|
|
depends on it.
|
|
- **`fleet-overlay/`** — templates for the FluxCD manifests that live in
|
|
the `anton-helm-workloads` repo. Not consumed from here — they're
|
|
versioned alongside the chart so the chart's contract with Flux stays
|
|
legible.
|
|
|
|
See `../DEPLOYMENT.md` for the end-to-end pipeline.
|