Files
templates/blueprints/zabbix/meta.json
Mauricio Siu c3de62fb83 feat: per-template metadata — eliminate meta.json merge conflicts
- move each template's metadata to blueprints/<id>/meta.json (442 files, byte-identical roundtrip with the old root meta.json)
- generate the served meta.json at build time into app/public/meta.json (gitignored); pnpm dev/build run the generator first
- CI validates every blueprints/<id>/meta.json via generate-meta.js --check (required fields, id/folder match, logo exists, folder<->meta bidirectionality) and rejects any committed root meta.json
- remove root meta.json, dedupe-and-sort-meta.js and build-scripts/process-meta.js (obsolete)
- update CONTRIBUTING.md, AGENTS.md and README.md

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-07 23:58:10 -06:00

19 lines
611 B
JSON

{
"id": "zabbix",
"name": "Zabbix",
"version": "7.4",
"description": "Zabbix is an open-source enterprise-grade monitoring platform for networks, servers, virtual machines, and cloud services. This template includes PostgreSQL, Nginx frontend, SNMP traps, and Java gateway.",
"logo": "image.png",
"links": {
"github": "https://github.com/zabbix/zabbix-docker",
"website": "https://www.zabbix.com/",
"docs": "https://www.zabbix.com/documentation/current/en/manual/installation/containers"
},
"tags": [
"monitoring",
"infrastructure",
"observability",
"alerting"
]
}