Document container build pattern and port navidrome #192

Merged
eblume merged 2 commits from feature/document-container-build-port-navidrome into main 2026-02-15 08:05:12 -08:00
Owner

Summary

  • Add how-to guide (docs/how-to/build-container-image.md) covering the full container build workflow: directory layout, Dagger local builds, mise release task, and common patterns with links to existing containers
  • Port navidrome from upstream deluan/navidrome:0.60.3 to a custom three-stage build (containers/navidrome/Dockerfile) using Node + Go + Alpine
  • Update navidrome deployment to use registry.ops.eblu.me/blumeops/navidrome:v1.0.0

Deployment and Testing

  • dagger call build --src=. --container-name=navidrome builds successfully
  • After merge: mise run container-tag-and-release navidrome v1.0.0
  • After image published: argocd app sync navidrome and verify pod starts
## Summary - Add how-to guide (`docs/how-to/build-container-image.md`) covering the full container build workflow: directory layout, Dagger local builds, mise release task, and common patterns with links to existing containers - Port navidrome from upstream `deluan/navidrome:0.60.3` to a custom three-stage build (`containers/navidrome/Dockerfile`) using Node + Go + Alpine - Update navidrome deployment to use `registry.ops.eblu.me/blumeops/navidrome:v1.0.0` ## Deployment and Testing - [x] `dagger call build --src=. --container-name=navidrome` builds successfully - [ ] After merge: `mise run container-tag-and-release navidrome v1.0.0` - [ ] After image published: `argocd app sync navidrome` and verify pod starts
Add a how-to guide covering the full container build workflow (Dagger build,
mise release task, Forgejo CI pipeline) and port navidrome from the upstream
deluan/navidrome image to a custom-built image in the zot registry.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
eblume merged commit 996441876d into main 2026-02-15 08:05:12 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
eblume/blumeops!192
No description provided.