Reusable Dockyard package catalog for common Docker Compose applications.
This repository is intentionally separate from nandub/dockyard:
dockyardis the package manager and CLI.dockyard-packagesis a catalog of reusable packages.
The packages are conservative starters. They are designed for local-first development, repeatable validation, and safe customization through values.yaml or external values files.
See docs/package-index.md for the generated index.
Infrastructure:
postgresredismariadbcaddytraefiknginxadminerpgadmin
Observability:
prometheusgrafanalokialloyuptime-kuma
Application platforms:
miniokeycloakrabbitmqnatsmeilisearchtypesense
Each package has:
Dockyard.yaml
compose.yaml
values.yaml
values.schema.json
README.md
SECURITY.md
LICENSE
.\scripts\verify.ps1On Linux/macOS:
./scripts/verify.shdockyard package lint .\packages\postgres --strict
dockyard package test .\packages\postgres --strictdockyard package .\packages\postgres -o .\dist\postgres-0.1.0.dockyard.tgzdockyard push .\dist\postgres-0.1.0.dockyard.tgz `
oci://ghcr.io/nandub/dockyard-packages/postgres:0.1.0- No package uses
latestimage tags. - Packages use named volumes instead of host path mounts.
- Host networking and privileged containers are disabled by policy.
- Docker socket mounts are avoided by default.
- Administrative UIs are examples only; expose them only on trusted networks.
- Development credentials are placeholders and must be overridden before real use.
- Secret-like values are marked with
x-dockyard-sensitivein schemas.
These packages are starters. Before production:
- Pin image tags to versions your team has reviewed.
- Use external values files or environment-backed values for secrets.
- Configure TLS and authentication at the edge.
- Review exposed ports.
- Run
dockyard package lint --strictanddockyard package test --strict. - Publish package archives to a registry you control.
MongoDB is included as an authentication-enabled, persistent, single-node replica set starter package.