mirror of
https://github.com/Dokploy/templates.git
synced 2026-07-08 23:45:24 +02:00
c3de62fb83
- 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>
19 lines
836 B
JSON
19 lines
836 B
JSON
{
|
|
"id": "vault",
|
|
"name": "Vault",
|
|
"version": "latest",
|
|
"description": "Vault is a tool for securely accessing secrets. A secret is anything that you want to tightly control access to, such as API keys, passwords, certificates, and more. Vault provides a unified interface to any secret, while providing tight access control and recording a detailed audit log. To sign in: In the Vault UI, select 'Token' as the authentication method (not GitHub), then enter the root token from the VAULT_DEV_ROOT_TOKEN_ID environment variable (auto-generated).",
|
|
"logo": "vault.svg",
|
|
"links": {
|
|
"github": "https://github.com/hashicorp/vault",
|
|
"website": "https://www.vaultproject.io/",
|
|
"docs": "https://developer.hashicorp.com/vault/docs"
|
|
},
|
|
"tags": [
|
|
"security",
|
|
"secrets",
|
|
"devops",
|
|
"infrastructure"
|
|
]
|
|
}
|