github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-07-16 04:48:50 -05:00
Code Issues 3.0k Packages Projects Releases Wiki Activity

[PR #710] [CLOSED] Add Obscreen blueprint template #2032

New Issue
Closed
opened 2026-04-20 11:03:29 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 11:03:29 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/710
Author: @jr-k
Created: 2/14/2026
Status: ❌ Closed

Base: canary ← Head: obscreen2

📝 Commits (6)

  • 3a38af3 Add Obscreen blueprint template
  • b6789e4 meta changes to obscreen blueprints
  • 445302a meta changes to obscreen blueprints
  • d6667b9 Merge branch 'Dokploy:canary' into obscreen
  • c8b9a79 some fixes from greptile-apps
  • 0f07390 Fix verison

📊 Changes

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

View changed files

➕ blueprints/obscreen/docker-compose.yml (+16 -0)
➕ blueprints/obscreen/obscreen.png (+0 -0)
➕ blueprints/obscreen/template.toml (+16 -0)
📝 meta.json (+22 -0)

📄 Description

What is this PR about?

New PR of Obscreen - a digital signage service

Checklist

Before submitting this PR, please make sure that:

Issues related (if applicable)

Close automatically the related issues using the keywords: closes #ISSUE_NUMBER

Screenshots or Videos

Greptile Overview

Greptile Summary

Added Obscreen digital signage template with proper Dokploy configuration structure.

  • New template includes docker-compose.yml, template.toml, logo, and meta.json entry
  • Template follows Dokploy conventions (no ports mapping, uses expose implicitly, proper service naming)
  • Configuration includes proper domain setup, environment variables, and persistent volumes
  • Missing required version: "3.8" field in docker-compose.yml
  • Using :latest tag instead of pinned version creates supply chain risk
  • Version mismatch between docker-compose.yml (:latest) and meta.json (2025.12.5)

Confidence Score: 3/5

  • This PR is safe to merge with minor fixes needed for compliance with template standards
  • Score reflects that the template follows most Dokploy conventions correctly (service naming, volume configuration, proper use of template.toml), but has one critical syntax issue (missing version field) and style/security recommendations (version pinning). The template structure is sound and functional, but needs the version field added to pass validation
  • Pay close attention to blueprints/obscreen/docker-compose.yml - requires version: "3.8" field at the top

Last reviewed commit: d6667b9

(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!

Context used:

  • Context from dashboard - 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/710 **Author:** [@jr-k](https://github.com/jr-k) **Created:** 2/14/2026 **Status:** ❌ Closed **Base:** `canary` ← **Head:** `obscreen2` --- ### 📝 Commits (6) - [`3a38af3`](https://github.com/Dokploy/templates/commit/3a38af398ddbd53681936080ef07823ac64ebaf5) Add Obscreen blueprint template - [`b6789e4`](https://github.com/Dokploy/templates/commit/b6789e48bbbceaaf0871b6b0b4783ae792b4c705) meta changes to obscreen blueprints - [`445302a`](https://github.com/Dokploy/templates/commit/445302ad7ebbcc805dcc450216e720fec837cad8) meta changes to obscreen blueprints - [`d6667b9`](https://github.com/Dokploy/templates/commit/d6667b9c9a61fff866b653a55f506968df081e84) Merge branch 'Dokploy:canary' into obscreen - [`c8b9a79`](https://github.com/Dokploy/templates/commit/c8b9a791d0e1268952a65c06242dbd0ed5ae0e4b) some fixes from greptile-apps - [`0f07390`](https://github.com/Dokploy/templates/commit/0f0739048a8be4760eb64a4a1b4efc50836e0cdd) Fix verison ### 📊 Changes **4 files changed** (+54 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/obscreen/docker-compose.yml` (+16 -0) ➕ `blueprints/obscreen/obscreen.png` (+0 -0) ➕ `blueprints/obscreen/template.toml` (+16 -0) 📝 `meta.json` (+22 -0) </details> ### 📄 Description ## What is this PR about? New PR of Obscreen - a digital signage service ## 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. ## Issues related (if applicable) Close automatically the related issues using the keywords: `closes #ISSUE_NUMBER` ## Screenshots or Videos - License file: [obscreen_license_64523153.zip](https://github.com/user-attachments/files/25314984/obscreen_license_64523153.zip) - Screenshot successfull deployment: https://cln.sh/ppXb4frK <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> Added Obscreen digital signage template with proper Dokploy configuration structure. - New template includes `docker-compose.yml`, `template.toml`, logo, and `meta.json` entry - Template follows Dokploy conventions (no ports mapping, uses `expose` implicitly, proper service naming) - Configuration includes proper domain setup, environment variables, and persistent volumes - Missing required `version: "3.8"` field in docker-compose.yml - Using `:latest` tag instead of pinned version creates supply chain risk - Version mismatch between docker-compose.yml (`:latest`) and meta.json (`2025.12.5`) <h3>Confidence Score: 3/5</h3> - This PR is safe to merge with minor fixes needed for compliance with template standards - Score reflects that the template follows most Dokploy conventions correctly (service naming, volume configuration, proper use of template.toml), but has one critical syntax issue (missing version field) and style/security recommendations (version pinning). The template structure is sound and functional, but needs the version field added to pass validation - Pay close attention to `blueprints/obscreen/docker-compose.yml` - requires `version: "3.8"` field at the top <sub>Last reviewed commit: d6667b9</sub> <!-- greptile_other_comments_section --> <sub>(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!</sub> **Context used:** - Context from `dashboard` - 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-20 11:03:29 -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#2032
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?