blumeops/argocd/manifests/mealie/kustomization.yaml at 11330ebea0b5ee314e7eade61fa44e48c597a3be - eblume/blumeops - Forgejo: Beyond coding. We Forge.

eblume/blumeops

Erich Blume 11330ebea0

Build Container (Nix) / detect (push) Successful in 2s

Details

Build Container / detect (push) Successful in 2s

Details

Build Container (Nix) / build (mealie) (push) Successful in 2s

Details

Build Container / build (mealie) (push) Successful in 8s

Details

Deploy Mealie recipe manager (#299 )

## Summary

- Deploy Mealie (self-hosted recipe manager) on minikube-indri via ArgoCD
- Build container from source via forge mirror (`mirrors/mealie`) — multi-stage Dockerfile with Node.js frontend + Python/uv backend
- Add Caddy proxy entry for `meals.ops.eblu.me`
- Part of a larger meal planning pipeline: Mealie stores categorized recipes, a planner script selects balanced meals, and Ollama generates unified cooking timelines

## Status

- [x] Mirror mealie repo on forge
- [x] Dockerfile (from-source build)
- [x] ArgoCD app + k8s manifests
- [x] Caddy proxy entry
- [x] Service docs, routing table, app registry
- [ ] Local Dagger build test
- [ ] Container build + push to registry
- [ ] Update kustomization.yaml with real image tag
- [ ] Deploy and verify
- [ ] Provision Caddy

## Test plan

- Build container locally via `dagger call build --src=. --container-name=mealie`
- Trigger CI build via `mise run container-build-and-release mealie`
- Deploy from branch: `argocd app set mealie --revision deploy-mealie && argocd app sync mealie`
- Verify Mealie UI at `https://meals.ops.eblu.me`
- Verify API docs at `https://meals.ops.eblu.me/docs`

Reviewed-on: #299

2026-03-16 21:59:10 -07:00

15 lines

281 B

YAML

Raw Blame History

 apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
 namespace: mealie
 resources:
   - deployment.yaml
   - service.yaml
   - pvc.yaml
   - ingress-tailscale.yaml
   - external-secret.yaml
 images:
   - name: registry.ops.eblu.me/blumeops/mealie
     newTag: v3.12.0-5c5fd18