feat(blueprint): add Verdaccio - private node.js package registry

[wladiarce]

What is this PR about?

New PR of [Template Name]

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.

Issues related (if applicable)

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

Screenshots or Videos

Greptile Summary

This PR adds a Verdaccio (private Node.js package registry) blueprint to the Dokploy templates collection. The template includes a docker-compose.yml, a template.toml with a fully embedded Verdaccio config (via [[config.mounts]]), an SVG logo, and a meta.json entry. The overall approach and configuration are correct; however, the docker-compose.yml violates two mandatory project conventions defined in AGENTS.md:

1. ports used instead of expose: Dokploy handles all external routing; using ports directly exposes port 4873 on the host rather than routing through Dokploy's managed reverse proxy.
2. Missing restart policy: The service does not define restart: unless-stopped (or restart: always), meaning the container will not automatically recover from crashes or host reboots.

Both issues are explicitly prohibited/required by the project's Docker Compose conventions and must be fixed before this template can be safely deployed.

Confidence Score: 2/5

• Not safe to merge — the docker-compose.yml violates two mandatory project conventions that will prevent safe deployment in Dokploy.
• The PR contains two verified violations of mandatory Docker Compose conventions defined in AGENTS.md. The use of ports instead of expose bypasses Dokploy's routing system and exposes the service directly on the host, while the missing restart policy means the service cannot recover automatically. Both must be fixed before deployment. The other files (meta.json, template.toml, and SVG) are correct.
• blueprints/verdaccio/docker-compose.yml requires fixing: replace ports with expose and add restart: unless-stopped

_{Last reviewed commit: fc72f73}

_{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!}

Context used:

• Rule from dashboard - AGENTS.md (source)

[dosubot]

Related Documentation

Checked 7 published document(s) in 1 knowledge base(s). No updates required.

^{How did I do? Any feedback?}  

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

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

[greptile-apps]

_{4 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

ports must be replaced with expose

Per the project's Docker Compose conventions (AGENTS.md), ports must never be included in blueprint files. Dokploy handles external routing via its own proxy, so using ports would expose port 4873 directly on the host instead of routing through Dokploy's managed network. Use expose instead to only announce the port to the Docker network.

Suggested change

	ports:
	- 4873
	expose:
	- 4873

Context Used: Rule from dashboard - AGENTS.md (source)

[greptile-apps]

Missing restart policy

Per the project's Docker Compose conventions (AGENTS.md), every service must include restart: unless-stopped or restart: always. Without this, the container will not automatically recover after a crash or host reboot.

Suggested change

	verdaccio:
	image: verdaccio/verdaccio:6
	verdaccio:
	image: verdaccio/verdaccio:6
	restart: unless-stopped

Context Used: Rule from dashboard - AGENTS.md (source)