I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
I have added tests that demonstrate that my correction works or that my new feature works.
Greptile Summary
This PR adds a new Windshift work management template to the Dokploy blueprint collection, with a properly configured docker-compose.yml, template.toml, and logo. The diff also removes a duplicate Strapi entry from meta.json — the canonical entry still exists earlier in the file (line 5918), so this is correct output from running dedupe-and-sort-meta.js.
Confidence Score: 5/5
This PR is safe to merge — the template follows all required conventions and introduces no breaking changes.
All required AGENTS.md conventions are satisfied: version 3.8, no ports/container_name/networks, restart policies on every service, named volumes, secrets generated via helpers, and version pinning. The meta.json entry has all required fields with a version matching the image tag. No P0 or P1 issues found.
The Strapi template entry has been deleted from meta.json, but blueprints/strapi/docker-compose.yml and blueprints/strapi/template.toml still exist in the repository. This appears to be an unintentional casualty of editing meta.json manually — likely a merge-conflict resolution that dropped the block. This will cause Strapi to disappear from the template registry even though its blueprint files remain intact.
Per project conventions, logos should be SVG (preferred, ~128×128 px). A PNG will work but SVG scales better in the UI. Consider converting to SVG if one is available upstream.
(2/5) Greptile learns from your feedback when you react with thumbs up/down!
🔄 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/787
**Author:** [@stefan-ernst](https://github.com/stefan-ernst)
**Created:** 4/14/2026
**Status:** ✅ Merged
**Merged:** 7/7/2026
**Merged by:** [@Siumauricio](https://github.com/Siumauricio)
**Base:** `canary` ← **Head:** `feature/windshift-updates`
---
### 📝 Commits (4)
- [`1fab171`](https://github.com/Dokploy/templates/commit/1fab171d4661a16dc538b08b40bee2d3f259266a) Adding Windshift for Dokploy
- [`a27b304`](https://github.com/Dokploy/templates/commit/a27b30413989aabe47a8d15535dd6e8a1ef48aea) Added up-to-date version and better tags
- [`e102a4d`](https://github.com/Dokploy/templates/commit/e102a4d29002d621c7b56e5b587f7e48eca8f5bc) Updated logo with less transparency
- [`6988012`](https://github.com/Dokploy/templates/commit/6988012b58ebd672721b0b37bfe11c4e9d17d827) Update docker-compose.yml with latest version
### 📊 Changes
**4 files changed** (+81 additions, -18 deletions)
<details>
<summary>View changed files</summary>
➕ `blueprints/windshift/docker-compose.yml` (+44 -0)
➕ `blueprints/windshift/template.toml` (+19 -0)
➕ `blueprints/windshift/windshift.png` (+0 -0)
📝 `meta.json` (+18 -18)
</details>
### 📄 Description
## What is this PR about?
Adding Windshift Work Management to Dokploy.
Windshift is a self-hosted work management system that's fast, complete, and simple to run.
I am personally using Dokploy as my PaaS and would love to see Windshift officially supported.
## 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.
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
This PR adds a new Windshift work management template to the Dokploy blueprint collection, with a properly configured `docker-compose.yml`, `template.toml`, and logo. The diff also removes a duplicate Strapi entry from `meta.json` — the canonical entry still exists earlier in the file (line 5918), so this is correct output from running `dedupe-and-sort-meta.js`.
<h3>Confidence Score: 5/5</h3>
- This PR is safe to merge — the template follows all required conventions and introduces no breaking changes.
- All required AGENTS.md conventions are satisfied: version 3.8, no ports/container_name/networks, restart policies on every service, named volumes, secrets generated via helpers, and version pinning. The meta.json entry has all required fields with a version matching the image tag. No P0 or P1 issues found.
- No files require special attention.
<!-- greptile_failed_comments -->
<details><summary><h3>Comments Outside Diff (2)</h3></summary>
1. `meta.json`, line 5952-5975 ([link](https://github.com/dokploy/templates/blob/a27b30413989aabe47a8d15535dd6e8a1ef48aea/meta.json#L5952-L5975))
<a href="#"><img alt="P1" src="https://greptile-static-assets.s3.amazonaws.com/badges/p1.svg?v=7" align="top"></a> **Strapi entry accidentally removed**
The Strapi template entry has been deleted from `meta.json`, but `blueprints/strapi/docker-compose.yml` and `blueprints/strapi/template.toml` still exist in the repository. This appears to be an unintentional casualty of editing `meta.json` manually — likely a merge-conflict resolution that dropped the block. This will cause Strapi to disappear from the template registry even though its blueprint files remain intact.
2. `blueprints/windshift/windshift.png`, line 1 ([link](https://github.com/dokploy/templates/blob/a27b30413989aabe47a8d15535dd6e8a1ef48aea/blueprints/windshift/windshift.png#L1))
<a href="#"><img alt="P2" src="https://greptile-static-assets.s3.amazonaws.com/badges/p2.svg?v=7" align="top"></a> **SVG format preferred for logo**
Per project conventions, logos should be SVG (preferred, ~128×128 px). A PNG will work but SVG scales better in the UI. Consider converting to SVG if one is available upstream.
**Context Used:** AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2))
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
</details>
<!-- /greptile_failed_comments -->
<sub>Reviews (2): Last reviewed commit: ["Updated logo with less transparency"](https://github.com/dokploy/templates/commit/e102a4d29002d621c7b56e5b587f7e48eca8f5bc) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=28325107)</sub>
<sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub>
<!-- /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/787
Author: @stefan-ernst
Created: 4/14/2026
Status: ✅ Merged
Merged: 7/7/2026
Merged by: @Siumauricio
Base:
canary← Head:feature/windshift-updates📝 Commits (4)
1fab171Adding Windshift for Dokploya27b304Added up-to-date version and better tagse102a4dUpdated logo with less transparency6988012Update docker-compose.yml with latest version📊 Changes
4 files changed (+81 additions, -18 deletions)
View changed files
➕
blueprints/windshift/docker-compose.yml(+44 -0)➕
blueprints/windshift/template.toml(+19 -0)➕
blueprints/windshift/windshift.png(+0 -0)📝
meta.json(+18 -18)📄 Description
What is this PR about?
Adding Windshift Work Management to Dokploy.
Windshift is a self-hosted work management system that's fast, complete, and simple to run.
I am personally using Dokploy as my PaaS and would love to see Windshift officially supported.
Checklist
Before submitting this PR, please make sure that:
Greptile Summary
This PR adds a new Windshift work management template to the Dokploy blueprint collection, with a properly configured
docker-compose.yml,template.toml, and logo. The diff also removes a duplicate Strapi entry frommeta.json— the canonical entry still exists earlier in the file (line 5918), so this is correct output from runningdedupe-and-sort-meta.js.Confidence Score: 5/5
Comments Outside Diff (2)
meta.json, line 5952-5975 (link)The Strapi template entry has been deleted from
meta.json, butblueprints/strapi/docker-compose.ymlandblueprints/strapi/template.tomlstill exist in the repository. This appears to be an unintentional casualty of editingmeta.jsonmanually — likely a merge-conflict resolution that dropped the block. This will cause Strapi to disappear from the template registry even though its blueprint files remain intact.blueprints/windshift/windshift.png, line 1 (link)Per project conventions, logos should be SVG (preferred, ~128×128 px). A PNG will work but SVG scales better in the UI. Consider converting to SVG if one is available upstream.
Context Used: AGENTS.md (source)
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Reviews (2): Last reviewed commit: "Updated logo with less transparency" | Re-trigger Greptile
(2/5) Greptile learns from your feedback when you react with thumbs up/down!
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.