mirror of
https://github.com/Dokploy/templates.git
synced 2026-07-15 14:52:05 -05:00
[PR #1014] [MERGED] feat: add MailCatcher NG template #16322
Reference in New Issue
Block a user
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?
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/1014
Author: @Siumauricio
Created: 7/14/2026
Status: ✅ Merged
Merged: 7/14/2026
Merged by: @Siumauricio
Base:
canary← Head:feat/mailcatcher-ng📝 Commits (1)
b7c2d6cfeat: add MailCatcher NG template📊 Changes
4 files changed (+67 additions, -0 deletions)
View changed files
➕
blueprints/mailcatcher-ng/docker-compose.yml(+27 -0)➕
blueprints/mailcatcher-ng/mailcatcher-ng.svg(+10 -0)➕
blueprints/mailcatcher-ng/meta.json(+17 -0)➕
blueprints/mailcatcher-ng/template.toml(+13 -0)📄 Description
What
Adds a template for MailCatcher NG (spaquet/mailcatcher), a lightweight SMTP catcher for development: it runs a simple SMTP server that captures every message sent to it and displays them in a web UI.
Closes #747
Decisions
stpaquet/alpinemailcatcher(the official Docker image from spaquet/docker-alpine-mailcatcher, v2.3.9, MailCatcher NG 1.6.8, Alpine 3.24.1). The registry only publishes alatesttag, so the image is pinned by digest (sha256:499c0e...) for reproducible deploys.expose, not published on the host): other apps in the same Dokploy project send mail tomailcatcher-ng:1025; the web UI (1080) is routed through the template domain.--persistenceflag and mounts a named volume at/home/mailcatcher/.mailcatcher, so captured mail survives restarts/redeploys.MAIL_LIMIT=50exposed as an env var (image default) to cap stored messages.wget --spideron the UI port.website_src/public/favicon.svg).Deploy test (demo instance)
Deployed on a Dokploy instance from this exact blueprint:
node build-scripts/generate-meta.js --checkpasses (477 templates validated).🤖 Generated with Claude Code
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.