Add frigate-notify nix container build #339

Merged

eblume merged 1 commit from feature/frigate-notify-local into main

2026-04-21 09:28:03 -07:00

eblume commented

2026-04-21 09:24:16 -07:00

Owner

Summary

Mirrors github.com/0x2142/frigate-notify at v0.5.4 to forge.ops.eblu.me/mirrors/frigate-notify.
Adds containers/frigate-notify/default.nix — buildGoModule + dockerTools.buildLayeredImage, following the ntfy pattern.
Uses -tags goolm to avoid the libolm CGO dependency (matrix notifier is imported unconditionally in the upstream but we only use ntfy alerts).
Runs as nonroot (UID 65534), exposes port 8000, bundles cacert/tzdata.

Why

Move ghcr.io/0x2142/frigate-notify:v0.5.4 (ringtail-deployed) under local control. Aligns with the indri → ringtail migration plan and the default.nix convention for ringtail-targeted containers documented in build-container-image.

Verification

dagger call build-nix --src=. --container-name=frigate-notify export --path=./out.tar.gz produces a valid 20MB docker archive (10 layers) with blumeops/frigate-notify tag locally.
Hashes pinned for fetchgit (src) and vendorHash (go modules).

Follow-up (post-merge)

mise run container-build-and-release frigate-notify — release from main SHA.
C0 follow-up: update argocd/manifests/frigate/kustomization.yaml image ref to registry.ops.eblu.me/blumeops/frigate-notify:v0.5.4-<sha>-nix.
ArgoCD auto-syncs the deployment.

Test plan

dagger call build-nix succeeds from a clean checkout.
mise run container-build-and-release frigate-notify --dry-run looks correct.
After release + kustomization swap: frigate-notify pod comes up healthy on ringtail; ntfy alerts still fire on Frigate events.

## Summary - Mirrors `github.com/0x2142/frigate-notify` at `v0.5.4` to `forge.ops.eblu.me/mirrors/frigate-notify`. - Adds `containers/frigate-notify/default.nix` — `buildGoModule` + `dockerTools.buildLayeredImage`, following the `ntfy` pattern. - Uses `-tags goolm` to avoid the libolm CGO dependency (matrix notifier is imported unconditionally in the upstream but we only use ntfy alerts). - Runs as nonroot (UID 65534), exposes port 8000, bundles `cacert`/`tzdata`. ## Why Move `ghcr.io/0x2142/frigate-notify:v0.5.4` (ringtail-deployed) under local control. Aligns with the [[indri → ringtail migration plan]] and the `default.nix` convention for ringtail-targeted containers documented in [[build-container-image]]. ## Verification - `dagger call build-nix --src=. --container-name=frigate-notify export --path=./out.tar.gz` produces a valid 20MB docker archive (10 layers) with `blumeops/frigate-notify` tag locally. - Hashes pinned for `fetchgit` (src) and `vendorHash` (go modules). ## Follow-up (post-merge) 1. `mise run container-build-and-release frigate-notify` — release from main SHA. 2. C0 follow-up: update `argocd/manifests/frigate/kustomization.yaml` image ref to `registry.ops.eblu.me/blumeops/frigate-notify:v0.5.4-<sha>-nix`. 3. ArgoCD auto-syncs the deployment. ## Test plan - [ ] `dagger call build-nix` succeeds from a clean checkout. - [ ] `mise run container-build-and-release frigate-notify --dry-run` looks correct. - [ ] After release + kustomization swap: frigate-notify pod comes up healthy on ringtail; ntfy alerts still fire on Frigate events.

eblume added 1 commit

2026-04-21 09:24:17 -07:00

Add frigate-notify nix container build 9a044b12c6

Mirrors 0x2142/frigate-notify at v0.5.4 and builds it locally with
buildGoModule + dockerTools.buildLayeredImage for the ringtail k3s
cluster. Uses the `goolm` build tag to avoid the libolm CGO dependency
(our alerting config only uses ntfy, but the matrix notifier is
imported unconditionally).

Kustomization update (image swap to registry.ops.eblu.me) will follow
post-merge once a main-SHA tag is released.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>