github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-05-06 02:07:03 -05:00
Code Issues 990 Packages Projects Releases Wiki Activity

[PR #778] [CLOSED] feat: add Glances system monitoring template #2893

New Issue
Closed
opened 2026-04-23 03:37:35 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-23 03:37:35 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/778
Author: @jyoti369
Created: 4/8/2026
Status: ❌ Closed

Base: main ← Head: feat/add-glances-template

📝 Commits (10+)

  • 1e21b7e feat(librechat): add LibreChat blueprint with compose, toml, metadata, links and tags
  • 758cf1d fix: rename templates to template.toml
  • 47daea9 fix(librechat): rename api service to librechat in docker-compose.yml
  • 3e8b431 Update blueprints/librechat/template.toml
  • 60796a9 Update blueprints/librechat/template.toml
  • 1d70294 fix(librechat): add version under [config] and remove stray [config.mounts] header
  • 2e1fb3b fix(librechat): remove predefined persistent volume mounts from template.toml
  • 46dc5b9 docs(librechat): add authentication reference link to docker-compose.yml
  • ac07aa2 feat: add Rote template
  • d58cc15 fix: process meta.json to fix formatting and sorting

📊 Changes

28 files changed (+964 additions, -105 deletions)

View changed files

📝 blueprints/convex/docker-compose.yml (+8 -8)
📝 blueprints/evolutionapi/docker-compose.yml (+1 -1)
➕ blueprints/glances/docker-compose.yml (+15 -0)
➕ blueprints/glances/glances.svg (+8 -0)
➕ blueprints/glances/template.toml (+11 -0)
📝 blueprints/grafana/docker-compose.yml (+1 -1)
➕ blueprints/imgproxy/docker-compose.yml (+76 -0)
➕ blueprints/imgproxy/imgproxy.png (+0 -0)
➕ blueprints/imgproxy/template.toml (+56 -0)
➕ blueprints/mediafetch/docker-compose.yml (+18 -0)
➕ blueprints/mediafetch/mediafetch.svg (+1 -0)
➕ blueprints/mediafetch/template.toml (+15 -0)
📝 blueprints/nextcloud-aio/docker-compose.yml (+14 -12)
➖ blueprints/nextcloud-aio/nextcloud-aio.svg (+0 -1)
➕ blueprints/nextcloud-aio/nextcloud.png (+0 -0)
📝 blueprints/nextcloud-aio/template.toml (+166 -12)
📝 blueprints/notifuse/docker-compose.yml (+28 -30)
📝 blueprints/notifuse/template.toml (+2 -17)
➕ blueprints/tuwunel/docker-compose.yml (+18 -0)
➕ blueprints/tuwunel/template.toml (+15 -0)

...and 8 more files

📄 Description

Description

Adds a Glances template — a cross-platform system monitoring tool written in Python with a web UI.

Closes #329 (partial — Dify portion still open, Flowise already exists)

/claim #152

Changes

  • blueprints/glances/docker-compose.yml: Single-service compose using the nicolargo/glances:4.3.0.8-full image with web mode enabled (-w flag), Docker socket mounted read-only for container monitoring, and a persistent volume for exports.
  • blueprints/glances/template.toml: Domain configuration pointing to port 61208 (Glances web UI default).
  • blueprints/glances/glances.svg: Official SVG logo from the upstream repository.
  • meta.json: Added Glances entry with monitoring tag. Also ran dedupe-and-sort-meta.js which removed a pre-existing duplicate Strapi entry.

Testing

  • Verified docker-compose.yml syntax
  • Verified template.toml structure matches existing templates (uptime-kuma, flowise)
  • Ran node dedupe-and-sort-meta.js — passed with no issues for the new entry
  • Logo renders correctly (5.2 KB SVG)

Glances Features

  • Real-time CPU, memory, disk, network monitoring
  • Docker container monitoring via mounted socket
  • Web UI accessible on port 61208
  • Export capabilities for metrics

Greptile Summary

Adds a Glances system-monitoring blueprint with a docker-compose.yml, template.toml, logo, and meta.json entry. The template follows Dokploy conventions (correct version, no ports, named volumes, service name matching folder), and a pre-existing duplicate Strapi entry is cleaned up as a side effect of running dedupe-and-sort-meta.js.

Confidence Score: 5/5

Safe to merge — all findings are P2 style suggestions that do not block functionality.

The template is structurally sound: correct Compose version, no ports/container_name/networks, service name matches folder, volumes declared, image pinned to a specific version, and meta.json entry is well-formed. The only issues are env = {} (should be env = [] per AGENTS.md) and an informational note about the elevated host access from pid: host + Docker socket — neither blocks merge.

blueprints/glances/template.toml (env syntax)

Vulnerabilities
  • pid: host + read-only Docker socket in blueprints/glances/docker-compose.yml: the container gets full visibility into host process tree and Docker daemon state. This is inherent to a system-monitor workload but should be disclosed to operators deploying in shared/multi-tenant Dokploy environments.

Reviews (1): Last reviewed commit: "feat: add Glances system monitoring temp..." | Re-trigger Greptile

Greptile also left 2 inline comments on this PR.

(4/5) You can add custom instructions or style guidelines for the agent here!

Context used:

  • Context used - AGENTS.md (source)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Dokploy/templates/pull/778 **Author:** [@jyoti369](https://github.com/jyoti369) **Created:** 4/8/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `feat/add-glances-template` --- ### 📝 Commits (10+) - [`1e21b7e`](https://github.com/Dokploy/templates/commit/1e21b7e785b5a2e1b5a604df57cd23d31a0d3955) feat(librechat): add LibreChat blueprint with compose, toml, metadata, links and tags - [`758cf1d`](https://github.com/Dokploy/templates/commit/758cf1d873d45ea0771c109cbcb6101fedc3ba79) fix: rename templates to template.toml - [`47daea9`](https://github.com/Dokploy/templates/commit/47daea92f862cf2d111d017b6f3e9da176455451) fix(librechat): rename api service to librechat in docker-compose.yml - [`3e8b431`](https://github.com/Dokploy/templates/commit/3e8b43103173503b19e93276aa9810f4fa8cba98) Update blueprints/librechat/template.toml - [`60796a9`](https://github.com/Dokploy/templates/commit/60796a90847bf27061eaba5491eb02c49400bdf2) Update blueprints/librechat/template.toml - [`1d70294`](https://github.com/Dokploy/templates/commit/1d702943103d80af380e68f9a274d14d2fd90223) fix(librechat): add version under [config] and remove stray [config.mounts] header - [`2e1fb3b`](https://github.com/Dokploy/templates/commit/2e1fb3b3a9ea2c277d593ca5891e744b0c01a7f6) fix(librechat): remove predefined persistent volume mounts from template.toml - [`46dc5b9`](https://github.com/Dokploy/templates/commit/46dc5b9be3ea8f06d931d709ded142d2f7a216a9) docs(librechat): add authentication reference link to docker-compose.yml - [`ac07aa2`](https://github.com/Dokploy/templates/commit/ac07aa2ed86c1ff47af34a3e50533ea2ce4946ff) feat: add Rote template - [`d58cc15`](https://github.com/Dokploy/templates/commit/d58cc15c54c09f2e8a5768c839d569a2d2d61ce0) fix: process meta.json to fix formatting and sorting ### 📊 Changes **28 files changed** (+964 additions, -105 deletions) <details> <summary>View changed files</summary> 📝 `blueprints/convex/docker-compose.yml` (+8 -8) 📝 `blueprints/evolutionapi/docker-compose.yml` (+1 -1) ➕ `blueprints/glances/docker-compose.yml` (+15 -0) ➕ `blueprints/glances/glances.svg` (+8 -0) ➕ `blueprints/glances/template.toml` (+11 -0) 📝 `blueprints/grafana/docker-compose.yml` (+1 -1) ➕ `blueprints/imgproxy/docker-compose.yml` (+76 -0) ➕ `blueprints/imgproxy/imgproxy.png` (+0 -0) ➕ `blueprints/imgproxy/template.toml` (+56 -0) ➕ `blueprints/mediafetch/docker-compose.yml` (+18 -0) ➕ `blueprints/mediafetch/mediafetch.svg` (+1 -0) ➕ `blueprints/mediafetch/template.toml` (+15 -0) 📝 `blueprints/nextcloud-aio/docker-compose.yml` (+14 -12) ➖ `blueprints/nextcloud-aio/nextcloud-aio.svg` (+0 -1) ➕ `blueprints/nextcloud-aio/nextcloud.png` (+0 -0) 📝 `blueprints/nextcloud-aio/template.toml` (+166 -12) 📝 `blueprints/notifuse/docker-compose.yml` (+28 -30) 📝 `blueprints/notifuse/template.toml` (+2 -17) ➕ `blueprints/tuwunel/docker-compose.yml` (+18 -0) ➕ `blueprints/tuwunel/template.toml` (+15 -0) _...and 8 more files_ </details> ### 📄 Description ## Description Adds a [Glances](https://github.com/nicolargo/glances) template — a cross-platform system monitoring tool written in Python with a web UI. Closes #329 (partial — Dify portion still open, Flowise already exists) /claim #152 ## Changes - **`blueprints/glances/docker-compose.yml`**: Single-service compose using the `nicolargo/glances:4.3.0.8-full` image with web mode enabled (`-w` flag), Docker socket mounted read-only for container monitoring, and a persistent volume for exports. - **`blueprints/glances/template.toml`**: Domain configuration pointing to port 61208 (Glances web UI default). - **`blueprints/glances/glances.svg`**: Official SVG logo from the upstream repository. - **`meta.json`**: Added Glances entry with monitoring tag. Also ran `dedupe-and-sort-meta.js` which removed a pre-existing duplicate Strapi entry. ## Testing - Verified `docker-compose.yml` syntax - Verified `template.toml` structure matches existing templates (uptime-kuma, flowise) - Ran `node dedupe-and-sort-meta.js` — passed with no issues for the new entry - Logo renders correctly (5.2 KB SVG) ## Glances Features - Real-time CPU, memory, disk, network monitoring - Docker container monitoring via mounted socket - Web UI accessible on port 61208 - Export capabilities for metrics <!-- greptile_comment --> <h3>Greptile Summary</h3> Adds a Glances system-monitoring blueprint with a `docker-compose.yml`, `template.toml`, logo, and `meta.json` entry. The template follows Dokploy conventions (correct version, no `ports`, named volumes, service name matching folder), and a pre-existing duplicate Strapi entry is cleaned up as a side effect of running `dedupe-and-sort-meta.js`. <h3>Confidence Score: 5/5</h3> Safe to merge — all findings are P2 style suggestions that do not block functionality. The template is structurally sound: correct Compose version, no ports/container_name/networks, service name matches folder, volumes declared, image pinned to a specific version, and meta.json entry is well-formed. The only issues are env = {} (should be env = [] per AGENTS.md) and an informational note about the elevated host access from pid: host + Docker socket — neither blocks merge. blueprints/glances/template.toml (env syntax) <details open><summary><h3>Vulnerabilities</h3></summary> - `pid: host` + read-only Docker socket in `blueprints/glances/docker-compose.yml`: the container gets full visibility into host process tree and Docker daemon state. This is inherent to a system-monitor workload but should be disclosed to operators deploying in shared/multi-tenant Dokploy environments. </details> <sub>Reviews (1): Last reviewed commit: ["feat: add Glances system monitoring temp..."](https://github.com/dokploy/templates/commit/5bd22d5142db71521ba9d1cd5a78c84445879c3d) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=27720271)</sub> > Greptile also left **2 inline comments** on this PR. <sub>(4/5) You can add custom instructions or style guidelines for the agent [here](https://app.greptile.com/review/github)!</sub> **Context used:** - Context used - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2)) <!-- /greptile_comment --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-23 03:37:35 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
pull-request
Mirrored from GitHub Pull Request
 template
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#2893
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?