github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-05-06 16:55:42 -05:00
Code Issues 990 Packages Projects Releases Wiki Activity

[PR #734] [CLOSED] Add verdaccio template #2054

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

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/734
Author: @wladiarce
Created: 3/3/2026
Status: ❌ Closed

Base: canary ← Head: add-verdaccio-template

📝 Commits (4)

📊 Changes

55 files changed (+1806 additions, -123 deletions)

View changed files

📝 AGENTS.md (+10 -0)
📝 CONTRIBUTING.md (+5 -0)
📝 blueprints/ackee/instructions.md (+1 -1)
📝 blueprints/alist/docker-compose.yml (+1 -1)
📝 blueprints/appsmith/docker-compose.yml (+6 -2)
📝 blueprints/budibase/docker-compose.yml (+12 -25)
➕ blueprints/cloudflare-ddns/cloudflare-ddns.svg (+8 -0)
➕ blueprints/cloudflare-ddns/docker-compose.yml (+16 -0)
➕ blueprints/cloudflare-ddns/template.toml (+9 -0)
📝 blueprints/cloudflared/docker-compose.yml (+2 -2)
📝 blueprints/cloudflared/template.toml (+3 -1)
📝 blueprints/habitica/docker-compose.yml (+66 -9)
📝 blueprints/habitica/template.toml (+16 -8)
📝 blueprints/invoiceshelf/docker-compose.yml (+2 -4)
➕ blueprints/ipfs/docker-compose.yml (+17 -0)
➕ blueprints/ipfs/ipfs.svg (+1 -0)
➕ blueprints/ipfs/template.toml (+25 -0)
➕ blueprints/moltbot/docker-compose.yml (+35 -0)
➕ blueprints/moltbot/moltbot.svg (+60 -0)
➕ blueprints/moltbot/template.toml (+18 -0)

...and 35 more files

📄 Description

What is this PR about?

New PR of Verdaccio

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

image image

Greptile Summary

This PR adds a new Verdaccio (private npm proxy registry) template along with updates to existing blueprints and documentation improvements. The template.toml for Verdaccio is well-constructed with complete default configuration, but the docker-compose.yml has two mandatory convention violations from AGENTS.md:

  1. Uses ports instead of expose (line 8–9): The project explicitly forbids ports directives; Dokploy manages all routing, so only expose should be used.
  2. Missing restart policy (line 5): Every service must declare restart: unless-stopped or restart: always for automatic recovery from crashes and reboots.

Both violations are documented as non-negotiable in the project's Docker Compose conventions and should be fixed before merge.

Confidence Score: 1/5

  • Not safe to merge — the Verdaccio docker-compose.yml violates two mandatory project conventions that prevent Dokploy from correctly managing the service.
  • The Verdaccio docker-compose.yml file violates two critical, non-negotiable conventions from AGENTS.md. The ports directive is explicitly forbidden (only expose is allowed) because Dokploy manages all routing. The missing restart policy violates mandatory requirements for service resilience. These are not style issues or suggestions—they are blocking violations of the project's Docker Compose specification that must be corrected before the template can be merged.
  • blueprints/verdaccio/docker-compose.yml — requires fixes for both ports→expose and addition of restart directive

Last reviewed commit: 31d6804

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

Context used:

  • Rule 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/734 **Author:** [@wladiarce](https://github.com/wladiarce) **Created:** 3/3/2026 **Status:** ❌ Closed **Base:** `canary` ← **Head:** `add-verdaccio-template` --- ### 📝 Commits (4) - [`9d17e6b`](https://github.com/Dokploy/templates/commit/9d17e6bf8a2fafb26fb692740352d6ed7386d68a) New Templates (#690) - [`c818352`](https://github.com/Dokploy/templates/commit/c8183527214a7ee21d784950a466bb26364e0fc3) New version (#708) - [`39fb9dd`](https://github.com/Dokploy/templates/commit/39fb9dd134b0085e044abe13bfbe015b57096ef5) New templates (#711) - [`31d6804`](https://github.com/Dokploy/templates/commit/31d6804490fd8f0bfe2dbab7554f4d316608e2e1) feat(blueprint): add Verdaccio - private node.js package registry ### 📊 Changes **55 files changed** (+1806 additions, -123 deletions) <details> <summary>View changed files</summary> 📝 `AGENTS.md` (+10 -0) 📝 `CONTRIBUTING.md` (+5 -0) 📝 `blueprints/ackee/instructions.md` (+1 -1) 📝 `blueprints/alist/docker-compose.yml` (+1 -1) 📝 `blueprints/appsmith/docker-compose.yml` (+6 -2) 📝 `blueprints/budibase/docker-compose.yml` (+12 -25) ➕ `blueprints/cloudflare-ddns/cloudflare-ddns.svg` (+8 -0) ➕ `blueprints/cloudflare-ddns/docker-compose.yml` (+16 -0) ➕ `blueprints/cloudflare-ddns/template.toml` (+9 -0) 📝 `blueprints/cloudflared/docker-compose.yml` (+2 -2) 📝 `blueprints/cloudflared/template.toml` (+3 -1) 📝 `blueprints/habitica/docker-compose.yml` (+66 -9) 📝 `blueprints/habitica/template.toml` (+16 -8) 📝 `blueprints/invoiceshelf/docker-compose.yml` (+2 -4) ➕ `blueprints/ipfs/docker-compose.yml` (+17 -0) ➕ `blueprints/ipfs/ipfs.svg` (+1 -0) ➕ `blueprints/ipfs/template.toml` (+25 -0) ➕ `blueprints/moltbot/docker-compose.yml` (+35 -0) ➕ `blueprints/moltbot/moltbot.svg` (+60 -0) ➕ `blueprints/moltbot/template.toml` (+18 -0) _...and 35 more files_ </details> ### 📄 Description ## What is this PR about? New PR of Verdaccio ## 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 <img width="1039" height="763" alt="image" src="https://github.com/user-attachments/assets/dbd8a579-ebb3-45e0-aee1-39161930b0a5" /> <img width="1256" height="942" alt="image" src="https://github.com/user-attachments/assets/58c1e311-9af2-4e1e-9de4-08fa5b450c53" /> <!-- greptile_comment --> <h3>Greptile Summary</h3> This PR adds a new Verdaccio (private npm proxy registry) template along with updates to existing blueprints and documentation improvements. The `template.toml` for Verdaccio is well-constructed with complete default configuration, but the `docker-compose.yml` has two mandatory convention violations from `AGENTS.md`: 1. **Uses `ports` instead of `expose`** (line 8–9): The project explicitly forbids `ports` directives; Dokploy manages all routing, so only `expose` should be used. 2. **Missing `restart` policy** (line 5): Every service must declare `restart: unless-stopped` or `restart: always` for automatic recovery from crashes and reboots. Both violations are documented as non-negotiable in the project's Docker Compose conventions and should be fixed before merge. <h3>Confidence Score: 1/5</h3> - Not safe to merge — the Verdaccio docker-compose.yml violates two mandatory project conventions that prevent Dokploy from correctly managing the service. - The Verdaccio docker-compose.yml file violates two critical, non-negotiable conventions from AGENTS.md. The `ports` directive is explicitly forbidden (only `expose` is allowed) because Dokploy manages all routing. The missing `restart` policy violates mandatory requirements for service resilience. These are not style issues or suggestions—they are blocking violations of the project's Docker Compose specification that must be corrected before the template can be merged. - blueprints/verdaccio/docker-compose.yml — requires fixes for both `ports`→`expose` and addition of `restart` directive <sub>Last reviewed commit: 31d6804</sub> <!-- greptile_other_comments_section --> <sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub> **Context used:** - Rule 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:04:28 -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#2054
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?