[PR #661] [CLOSED] Add wings template #3399

New Issue

GiteaMirror · 2026-04-25T18:05:49-05:00

GiteaMirror commented

2026-04-25 18:05:49 -05:00

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/661
Author: @zaralX
Created: 1/17/2026
Status: ❌ Closed

Base: canary ← Head: add-wings-template

📝 Commits (5)

f901da3 Wings template | docker-compose.yml
63eb87e Wings template | Created v1.11.11 template
f8d8837 Pterodacrtyl Wings | compose and meta fixes
c68dba2 Pterodacrtyl Wings | meta.json process-meta fix
e52747a Pterodactyl Wings | docker compose fix

📊 Changes

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

View changed files

➕ blueprints/wings/docker-compose.yml (+33 -0)
➕ blueprints/wings/pterodactyl.png (+0 -0)
➕ blueprints/wings/template.toml (+11 -0)
📝 meta.json (+16 -0)

📄 Description

What is this PR about?

New PR of Pterodacrtyl Wings Template

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.

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

Screenshots or Videos

Greptile Summary

This PR adds a new Dokploy template for Pterodactyl Wings (v1.11.11), the server control plane companion to Pterodactyl Panel. The template includes a docker-compose.yml, template.toml, logo image, and meta.json entry.

Key issues found:

docker-compose.yml uses ports instead of expose: The Dokploy template conventions require using expose rather than ports, since Dokploy manages its own networking and port routing. Using ports can cause host port conflicts.
Hardcoded Traefik labels should be removed: The compose file includes Traefik routing labels with a placeholder domain (your.wings.domain) and cert resolver (myresolver). Dokploy manages Traefik configuration automatically based on template.toml, so these labels are redundant and will likely conflict with Dokploy's routing.
The template.toml and meta.json entries are well-structured and follow the project conventions correctly.
The pinned image version (v1.11.11) matches between meta.json and docker-compose.yml, with a helpful comment explaining why the latest v1.12.0 is not used.

Confidence Score: 2/5

This PR needs changes to the docker-compose.yml before merging — the Traefik labels and ports configuration conflict with Dokploy conventions.
Score of 2 reflects two actionable issues in the docker-compose.yml: (1) use of ports instead of expose which violates project conventions and can cause host conflicts, and (2) hardcoded Traefik labels that will conflict with Dokploy's automatic routing. The template.toml and meta.json are correct, and the issues are straightforward to fix.
blueprints/wings/docker-compose.yml — needs ports changed to expose and Traefik labels removed.

_{Last reviewed commit: e52747a}

_{(2/5) Greptile learns from your feedback when you react with thumbs up/down!}

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/661 **Author:** [@zaralX](https://github.com/zaralX) **Created:** 1/17/2026 **Status:** ❌ Closed **Base:** `canary` ← **Head:** `add-wings-template` --- ### 📝 Commits (5) - [`f901da3`](https://github.com/Dokploy/templates/commit/f901da37962863deee06baa76736736a2c7dd45f) Wings template | docker-compose.yml - [`63eb87e`](https://github.com/Dokploy/templates/commit/63eb87ea17e47b802941d3098ddc1481d4bfbc54) Wings template | Created v1.11.11 template - [`f8d8837`](https://github.com/Dokploy/templates/commit/f8d8837a1a96b51d0e7be13492b705a6ce60f289) Pterodacrtyl Wings | compose and meta fixes - [`c68dba2`](https://github.com/Dokploy/templates/commit/c68dba290691ac5ec73113e0983b2e68dc7d78d2) Pterodacrtyl Wings | meta.json process-meta fix - [`e52747a`](https://github.com/Dokploy/templates/commit/e52747aaf1fdfaa019806c918fa013fe8d444945) Pterodactyl Wings | docker compose fix ### 📊 Changes **4 files changed** (+60 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/wings/docker-compose.yml` (+33 -0) ➕ `blueprints/wings/pterodactyl.png` (+0 -0) ➕ `blueprints/wings/template.toml` (+11 -0) 📝 `meta.json` (+16 -0) </details> ### 📄 Description ## What is this PR about? New PR of Pterodacrtyl Wings Template ## 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. - [ ] 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  <h3>Greptile Summary</h3> This PR adds a new Dokploy template for [Pterodactyl Wings](https://github.com/pterodactyl/wings) (v1.11.11), the server control plane companion to Pterodactyl Panel. The template includes a `docker-compose.yml`, `template.toml`, logo image, and `meta.json` entry. **Key issues found:** - **`docker-compose.yml` uses `ports` instead of `expose`**: The Dokploy template conventions require using `expose` rather than `ports`, since Dokploy manages its own networking and port routing. Using `ports` can cause host port conflicts. - **Hardcoded Traefik labels should be removed**: The compose file includes Traefik routing labels with a placeholder domain (`your.wings.domain`) and cert resolver (`myresolver`). Dokploy manages Traefik configuration automatically based on `template.toml`, so these labels are redundant and will likely conflict with Dokploy's routing. - The `template.toml` and `meta.json` entries are well-structured and follow the project conventions correctly. - The pinned image version (v1.11.11) matches between `meta.json` and `docker-compose.yml`, with a helpful comment explaining why the latest v1.12.0 is not used. <h3>Confidence Score: 2/5</h3> - This PR needs changes to the docker-compose.yml before merging — the Traefik labels and ports configuration conflict with Dokploy conventions. - Score of 2 reflects two actionable issues in the docker-compose.yml: (1) use of `ports` instead of `expose` which violates project conventions and can cause host conflicts, and (2) hardcoded Traefik labels that will conflict with Dokploy's automatic routing. The template.toml and meta.json are correct, and the issues are straightforward to fix. - `blueprints/wings/docker-compose.yml` — needs `ports` changed to `expose` and Traefik labels removed. <sub>Last reviewed commit: e52747a</sub>  <sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub> **Context used:** - Context from `dashboard` - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2))  --- <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-25 18:05:49 -05:00

GiteaMirror closed this issue

2026-04-25 18:05:50 -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#3399