AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
翻譯準備中
瀏覽 Nomploy 精選的 Nomad Pack 登錄庫——即開即用,一鍵部署的基礎設施套件,適用於 Nomad:資料庫、可觀測性、開發工具與您自行託管的應用程式。
AI 翻譯
Browse the Nomploy curated Nomad Pack registry — batteries-included, one-click infrastructure packs for Nomad: databases, observability, dev tools, and apps you self-host.
開發工具HCL · Go TemplateGitHub @Nomploy上線中營運者未確認
試用過了嗎? 點一下就好,不需要登入。
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證為 nomploy 精選的 Nomad Pack 登錄庫(包括 zot 登錄等)。
AI 翻譯
Curated Nomad Pack registry for nomploy (zot registry, and more).
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
A curated Nomad Pack
registry for nomploy — one-command,
batteries-included infrastructure for a Nomad cluster.
The HashiCorp community registry doesn't carry container-registry, storage, or
observability packs, so these fill the gaps nomploy users hit.
Browse the catalog: https://packs.nomploy.com/ ·
JSON API: /api/packs.json
In nomploy: create a Compose service, set the type to Nomad Pack, set the
pack (e.g. zot) and this repo as the custom registry — then Deploy.
The live catalog is always current — it's
generated straight from these directories.檢視完整 README ↗A curated Nomad Pack registry for nomploy — one-command, batteries-included infrastructure for a Nomad cluster.
The HashiCorp community registry doesn't carry container-registry, storage, or observability packs, so these fill the gaps nomploy users hit.
Browse the catalog: https://packs.nomploy.com/ ·
JSON API: /api/packs.json
nomad-pack registry add nomploy github.com/Nomploy/nomad-packs
nomad-pack run zot --registry nomploy
In nomploy: create a Compose service, set the type to Nomad Pack, set the
pack (e.g. zot) and this repo as the custom registry — then Deploy.
| Category | Packs |
|---|---|
| Databases | postgres, mariadb, redis, clickhouse |
| Object storage | seaweedfs |
| Messaging | rabbitmq, nats |
| Observability | monitoring (Prometheus + node-exporter + cAdvisor + Grafana), loki, grafana |
| Identity | keycloak, vaultwarden |
| Dev tools | gitea, zot, adminer |
| Automation | n8n |
| Analytics | metabase |
| Apps | nginx, uptime-kuma |
| Device management | fleet |
The live catalog is always current — it's generated straight from these directories.
packs/<id>/
metadata.hcl # name / version / description / urls
variables.hcl # inputs
templates/<id>.nomad.tpl # the job (Go template, [[ ]] delimiters, v2 parser)
outputs.tpl # post-deploy hints
README.md · CHANGELOG.md
See AGENTS.md for how to author a pack (conventions, the v2 template syntax, volumes/ownership, all-in-one patterns).
Before opening a PR:
node scripts/lint-packs.mjs # static format checks
scripts/validate-packs.sh # render + `nomad job validate` each pack
CI runs both on every PR touching packs/**, and publishes the site + JSON API to GitHub
Pages on merge to master.
renovate.json configures Renovate to track
the container image tags in each pack's variables.hcl (a custom manager matches the *image
variable defaults as Docker deps). It bumps version-pinned tags (e.g. postgres:16-alpine,
typesense:27.1) via PRs; images left on :latest aren't version-bumped. Enable the Renovate
GitHub App on the repo for it to run.
Apache-2.0.