feat: add Glances system monitoring template

[jyoti369]

What this does

Adds a Glances template for system monitoring. Glances is a popular Python-based tool with a built-in web UI that shows CPU, memory, disk, network stats and Docker container info.

Partially addresses #329 (the Dify portion is still open, Flowise already exists as a template).

What's included

• blueprints/glances/docker-compose.yml - single service using the nicolargo/glances:4.3.0.8-full image with web mode, Docker socket mounted read-only for container monitoring, persistent volume for exports
• blueprints/glances/template.toml - domain config pointing to port 61208 (Glances web UI default)
• blueprints/glances/glances.svg - official logo from the upstream repo
• meta.json - new entry with monitoring tag, ran dedupe-and-sort-meta.js which also cleaned up a pre-existing duplicate Strapi entry

Note on authentication

Glances web mode doesn't support non-interactive password setup in Docker (the --password flag prompts for input on stdin, which hangs the container). This matches how other monitoring templates like beszel and uptime-kuma are set up in this repo. Users who need auth can put Glances behind a reverse proxy or configure a glances.conf with SSL certs.

Testing

• Verified docker-compose and template.toml match existing template conventions (uptime-kuma, flowise)
• node dedupe-and-sort-meta.js passes clean
• Logo renders correctly (5.2 KB SVG)

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	265e77b

[jyoti369]

Pushed a fix addressing the review comments:

• Added GLANCES_USERNAME/GLANCES_PASSWORD env vars with --password flag in GLANCES_OPT to secure the web UI
• Added GLANCES_PASSWORD to template.toml env config so Dokploy prompts for it during setup
• Added a comment explaining why pid:host is needed (Glances requires it to see host processes)
• Docker socket is already mounted read-only (:ro), which is the minimum privilege needed for container monitoring