Community-curated Docker Compose templates for Arcane.
Important
The community registry has been updated to the new url https://registry.getarcane.app/registry.json, the old registry at https://templates.arcane.ofkm.dev/registry.json is considered deprecated and will be removed in the future
Add this URL in Arcane’s Templates settings:
https://registry.getarcane.app/registry.json
- Source of truth: each template lives under
templates/<id>/and includes:compose.yaml(or docker-compose.yml/.yaml).env.exampletemplate.json(metadata; see example below)
- Auto-generation: scripts/build-registry.ts scans
templates/and generates registry.json that follows schema.json. - Do not edit or commit
registry.jsonin PRs — CI builds and publishes it on merge tomain. - Versioning policy: the registry version auto-bumps (minor by default) when a new template ID is added.
- CI: GitHub Actions type-checks, generates, validates against the schema, and commits updated
registry.json.
-
Fork this repo
-
Create a directory in
templates/using a lowercase, hyphenated ID:
cd templates
mkdir my-awesome-template- Add required files:
templates/my-awesome-template/
├─ compose.yaml # or docker-compose.yml/.yaml, compose.yml
├─ .env.example
└─ template.json
- template.json example:
{
"name": "My Awesome Template",
"description": "What it does and why it’s useful.",
"version": "1.0.0",
"author": "Your Name or Org",
"tags": ["category", "another-tag"]
}- Test locally (Node 24+, pnpm):
pnpm install
pnpm run type-check
pnpm run validate- Open a Pull Request
Tips:
- The generator accepts compose files named: compose.yaml, docker-compose.yml, docker-compose.yaml, compose.yml.
.env.exampleis required.- Tags should be lowercase, hyphenated.
- Validate data against the registry schema: schema.json
- Run locally on macOS:
pnpm install
pnpm run validateCommunity contributions welcome. By contributing you agree your changes are licensed under the repository’s license.