A template registry of my arcane compose templates. https://getarcane.app/docs/templates/registries
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Scott ab381f00fa Add Glances system monitoring template
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-16 13:14:51 -06:00
scripts Use tailnet LOCAL_URL defaults in x-arcane metadata 2026-02-13 10:33:03 -06:00
templates Add Glances system monitoring template 2026-05-16 13:14:51 -06:00
global.env.example Use tailnet LOCAL_URL defaults in x-arcane metadata 2026-02-13 10:33:03 -06:00
README.md Generate Arcane template registry from compose stacks 2026-02-12 14:04:30 -06:00
registry.json Add Glances system monitoring template 2026-05-16 13:14:51 -06:00

Arcane Compose Templates

Generated Arcane template registry from /home/docker/compose.

Layout

  • registry.json: Arcane registry index
  • templates/<id>/compose.yaml: Compose template
  • templates/<id>/.env.example: template variables
  • templates/<id>/README.md: template notes
  • global.env.example: shared variables to copy to /home/docker/global.env

Generate/Refresh

./scripts/generate_templates.py

Global Env and Permissions

Templates are normalized to use environment-driven identity settings (PUID, PGID, TZ) so mounts under /home/docker and NFS-backed paths keep predictable ownership.

Use global.env.example as your server baseline, then adjust per-server values before deploying templates.