[PR #742] [CLOSED] Add Tracearr template - Real-time monitoring for Plex, Jellyfin, and Emby servers. #5060

Closed
opened 2026-05-06 17:53:53 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/742
Author: @Yuri-NagaSaki
Created: 3/11/2026
Status: Closed

Base: canaryHead: add-tracearr


📝 Commits (1)

  • cfb4b26 Add Tracearr template - Real-time monitoring for Plex, Jellyfin, and Emby servers

📊 Changes

4 files changed (+91 additions, -0 deletions)

View changed files

blueprints/tracearr/docker-compose.yml (+47 -0)
blueprints/tracearr/logo.png (+0 -0)
blueprints/tracearr/template.toml (+23 -0)
📝 meta.json (+21 -0)

📄 Description

What is this PR about?

New PR of Tracearr - A real-time monitoring dashboard for Plex, Jellyfin, and Emby media servers. Track active streams, analyze playback metrics, and detect account sharing from
a single interface. Built on PostgreSQL 18 with TimescaleDB and Redis.

Checklist

Before submitting this PR, please make sure that:

Screenshots or Videos

image image image

Greptile Summary

This PR adds a new Tracearr template — a real-time monitoring dashboard for Plex, Jellyfin, and Emby media servers backed by TimescaleDB (PostgreSQL 18) and Redis. The overall structure follows the blueprint conventions, but there are a few issues that need to be resolved before this is ready to merge.

  • Breaking: template.toml uses a TOML table with key-value assignment syntax for the env block instead of the required array-of-strings format. This will cause the template to fail when parsed by Dokploy.
  • Convention: docker-compose.yml declares version: "3.9", but the project requires version: "3.8" per AGENTS.md.
  • Security: All three Docker images (tracearr:latest, timescaledb-ha:pg18, redis:7-alpine) use floating tags. AGENTS.md explicitly requires images to be pinned to specific versions to prevent supply-chain risks.
  • Discoverability: The meta.json description does not mention Plex, Jellyfin, or Emby — the primary use case — and the tags omit relevant terms such as plex, jellyfin, emby, and media.

Confidence Score: 1/5

  • Not safe to merge — the env configuration format in template.toml is broken and will prevent the template from deploying correctly.
  • The template.toml uses TOML object/table syntax for env variables, which is incompatible with the Dokploy template parser that expects an array of strings. This is a functional blocker. Additional issues include a wrong compose version, unpinned Docker images, and an inaccurate meta.json description.
  • blueprints/tracearr/template.toml requires a fix to the env format before this template will work.

Last reviewed commit: 461928a

Greptile also left 4 inline comments on this PR.

Context used:

  • Rule 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/742 **Author:** [@Yuri-NagaSaki](https://github.com/Yuri-NagaSaki) **Created:** 3/11/2026 **Status:** ❌ Closed **Base:** `canary` ← **Head:** `add-tracearr` --- ### 📝 Commits (1) - [`cfb4b26`](https://github.com/Dokploy/templates/commit/cfb4b26c698343d3d786a857074b98771c9801d1) Add Tracearr template - Real-time monitoring for Plex, Jellyfin, and Emby servers ### 📊 Changes **4 files changed** (+91 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/tracearr/docker-compose.yml` (+47 -0) ➕ `blueprints/tracearr/logo.png` (+0 -0) ➕ `blueprints/tracearr/template.toml` (+23 -0) 📝 `meta.json` (+21 -0) </details> ### 📄 Description ## What is this PR about? New PR of **Tracearr** - A real-time monitoring dashboard for Plex, Jellyfin, and Emby media servers. Track active streams, analyze playback metrics, and detect account sharing from a single interface. Built on PostgreSQL 18 with TimescaleDB and Redis. ## Checklist Before submitting this PR, please make sure that: - [x] I have read the suggestions in the README.md file https://github.com/Dokploy/templates?tab=readme-ov-file#general-requirements-when-creating-a-template - [x] I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong. - [x] I have added tests that demonstrate that my correction works or that my new feature works. ## Screenshots or Videos <img width="2982" height="1670" alt="image" src="https://github.com/user-attachments/assets/80af1940-fd0e-4252-9027-4d0fb98f938c" /> <img width="3022" height="1609" alt="image" src="https://github.com/user-attachments/assets/edc314f4-0e6a-4d42-a139-64754485fe21" /> <img width="1821" height="1642" alt="image" src="https://github.com/user-attachments/assets/47381314-5be9-497a-9c16-eadc74a6fffb" /> <!-- greptile_comment --> <h3>Greptile Summary</h3> This PR adds a new Tracearr template — a real-time monitoring dashboard for Plex, Jellyfin, and Emby media servers backed by TimescaleDB (PostgreSQL 18) and Redis. The overall structure follows the blueprint conventions, but there are a few issues that need to be resolved before this is ready to merge. - **Breaking**: `template.toml` uses a TOML table with key-value assignment syntax for the env block instead of the required array-of-strings format. This will cause the template to fail when parsed by Dokploy. - **Convention**: `docker-compose.yml` declares `version: "3.9"`, but the project requires `version: "3.8"` per AGENTS.md. - **Security**: All three Docker images (`tracearr:latest`, `timescaledb-ha:pg18`, `redis:7-alpine`) use floating tags. AGENTS.md explicitly requires images to be pinned to specific versions to prevent supply-chain risks. - **Discoverability**: The `meta.json` description does not mention Plex, Jellyfin, or Emby — the primary use case — and the tags omit relevant terms such as `plex`, `jellyfin`, `emby`, and `media`. <h3>Confidence Score: 1/5</h3> - Not safe to merge — the env configuration format in template.toml is broken and will prevent the template from deploying correctly. - The `template.toml` uses TOML object/table syntax for env variables, which is incompatible with the Dokploy template parser that expects an array of strings. This is a functional blocker. Additional issues include a wrong compose version, unpinned Docker images, and an inaccurate meta.json description. - `blueprints/tracearr/template.toml` requires a fix to the env format before this template will work. <sub>Last reviewed commit: 461928a</sub> > Greptile also left **4 inline comments** on this PR. **Context used:** - Rule 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-05-06 17:53:53 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#5060