This PR adds a new blueprint template for Obscreen, a digital signage service. The template includes a docker-compose.yml, template.toml, logo image, and a meta.json entry.
Version mismatch: The meta.json entry lists version 2025.12.5, but the Docker image in docker-compose.yml is obscreen/obscreen:v2026.1.6. These must be kept in sync per repository conventions.
The template structure is otherwise well-formed: it uses a generated secret key, configures the external URL with HTTPS, and defines appropriate named volumes for data persistence.
The docker-compose.yml omits the version: "3.8" declaration, which is still the documented convention per repository guidelines, though many existing templates also omit it.
Confidence Score: 3/5
This PR needs a minor fix for the version mismatch between meta.json and docker-compose.yml before merging.
The template is structurally sound with proper volume mounts, secret generation, and HTTPS configuration. However, the version mismatch between meta.json (2025.12.5) and docker-compose.yml (v2026.1.6) is a clear inconsistency that violates repository conventions and should be corrected before merge.
meta.json needs its version field updated to match the Docker image tag in docker-compose.yml
🔄 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/713
**Author:** [@jr-k](https://github.com/jr-k)
**Created:** 2/18/2026
**Status:** ❌ Closed
**Base:** `canary` ← **Head:** `obscreen3`
---
### 📝 Commits (10+)
- [`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
- [`e46282c`](https://github.com/Dokploy/templates/commit/e46282c3eb4c53d587688bd51da7144dc7890da6) bot fixes
- [`c0b9b92`](https://github.com/Dokploy/templates/commit/c0b9b92152585a8010d6bd526d87b36020d59d85) bot fixes
- [`df78e5f`](https://github.com/Dokploy/templates/commit/df78e5fcdd847d677b46fd5bae0331db91b25c06) Merge branch 'Dokploy:canary' into obscreen3
- [`800ea15`](https://github.com/Dokploy/templates/commit/800ea15b86bca128686a7cedb52163e15b5e1ed9) obscreen description change
### 📊 Changes
**4 files changed** (+56 additions, -0 deletions)
<details>
<summary>View changed files</summary>
➕ `blueprints/obscreen/docker-compose.yml` (+18 -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/25388585/obscreen_license_64523153.zip)
- Screenshot successfull deployment: https://cln.sh/ppXb4frK
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
This PR adds a new blueprint template for [Obscreen](https://obscreen.io/), a digital signage service. The template includes a `docker-compose.yml`, `template.toml`, logo image, and a `meta.json` entry.
- **Version mismatch**: The `meta.json` entry lists version `2025.12.5`, but the Docker image in `docker-compose.yml` is `obscreen/obscreen:v2026.1.6`. These must be kept in sync per repository conventions.
- The template structure is otherwise well-formed: it uses a generated secret key, configures the external URL with HTTPS, and defines appropriate named volumes for data persistence.
- The `docker-compose.yml` omits the `version: "3.8"` declaration, which is still the documented convention per repository guidelines, though many existing templates also omit it.
<h3>Confidence Score: 3/5</h3>
- This PR needs a minor fix for the version mismatch between meta.json and docker-compose.yml before merging.
- The template is structurally sound with proper volume mounts, secret generation, and HTTPS configuration. However, the version mismatch between meta.json (2025.12.5) and docker-compose.yml (v2026.1.6) is a clear inconsistency that violates repository conventions and should be corrected before merge.
- meta.json needs its version field updated to match the Docker image tag in docker-compose.yml
<sub>Last reviewed commit: 0f07390</sub>
<!-- greptile_other_comments_section -->
<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 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>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/713
Author: @jr-k
Created: 2/18/2026
Status: ❌ Closed
Base:
canary← Head:obscreen3📝 Commits (10+)
3a38af3Add Obscreen blueprint templateb6789e4meta changes to obscreen blueprints445302ameta changes to obscreen blueprintsd6667b9Merge branch 'Dokploy:canary' into obscreenc8b9a79some fixes from greptile-apps0f07390Fix verisone46282cbot fixesc0b9b92bot fixesdf78e5fMerge branch 'Dokploy:canary' into obscreen3800ea15obscreen description change📊 Changes
4 files changed (+56 additions, -0 deletions)
View changed files
➕
blueprints/obscreen/docker-compose.yml(+18 -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_NUMBERScreenshots or Videos
License file: obscreen_license_64523153.zip
Screenshot successfull deployment: https://cln.sh/ppXb4frK
Greptile Summary
This PR adds a new blueprint template for Obscreen, a digital signage service. The template includes a
docker-compose.yml,template.toml, logo image, and ameta.jsonentry.meta.jsonentry lists version2025.12.5, but the Docker image indocker-compose.ymlisobscreen/obscreen:v2026.1.6. These must be kept in sync per repository conventions.docker-compose.ymlomits theversion: "3.8"declaration, which is still the documented convention per repository guidelines, though many existing templates also omit it.Confidence Score: 3/5
Last reviewed commit:
0f07390(4/5) You can add custom instructions or style guidelines for the agent here!
Context used:
dashboard- AGENTS.md (source)🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.