feat: add windshift to dokploy

[stefan-ernst]

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:

• 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
• 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.
• No files require special attention.

Comments Outside Diff (2)

1. meta.json, line 5952-5975 (link)

   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)

   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)

   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!}

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	e102a4d

[stefan-ernst]

Merge problem with strapi entry will be fixed first

[stefan-ernst]

Looks like Strapi was duplicated in the meta.json and instead at line 5919

[stefan-ernst]

Manually checked canary branch and indeed, strapi is duplicated