Add SafeLine WAF Compose Template
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
Feature Request: Add SafeLine WAF Compose Template
Summary
Please add a ready-to-use SafeLine WAF template to the Dokploy “Templates” / one-click deployment catalog. SafeLine is a self-hosted, reverse-proxy web application firewall designed to protect applications from common web attacks and malicious traffic. It would be a valuable addition for users who want to secure their Dokploy-hosted apps.
Why this is useful
- 🛡 Security: SafeLine provides protection against SQL injection, XSS, command injection, path traversal, SSRF, and more.
- 🤖 Bot Protection: Features like CAPTCHA challenges, rate limiting, and bot detection add an extra security layer.
- 📊 Visibility: Built-in logging and dashboards help monitor traffic and attacks.
- ⚙️ Reverse Proxy Ready: Runs as a front-end to other Dokploy services, making it easy to slot in before apps like Appwrite, Ghost, WordPress, or custom APIs.
- 🌍 Open Source: SafeLine has an active community and is under active development.
🙌 Thanks for considering! This would make Dokploy an even more secure and versatile platform for self-hosting.
Describe the solution you'd like
I would like Dokploy to include a SafeLine WAF compose template in the Marketplace, so that users can easily deploy it as a reverse proxy in front of their applications. The template should provide sensible defaults (ports 80/443, volumes for config/logs/certs, and admin credentials) and allow linking protected apps as upstreams directly from the Dokploy UI. This would make it simple to secure any service deployed via Dokploy with SafeLine’s web application firewall and bot protection features.
Describe alternatives you've considered
Alternatives Considered
Right now, users can manually integrate SafeLine by editing custom docker-compose.yml files, but a first-class template would:
- Standardize configuration
- Lower the barrier for adoption
- Ensure better integration with Dokploy’s reverse proxy and SSL management
Additional context
References
- SafeLine GitHub: https://github.com/chaitin/SafeLine
- SafeLine Website: [https://safepoint.cloud/landing/safeline](https://safepoint.cloud/landing/safeline
Will you send a PR to implement it?
Maybe, need help
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating Dokploy’s Templates or one-click deployment catalog and reviewing how existing Docker Compose templates are defined. Compare SafeLine’s deployment requirements with the catalog’s supported configuration, then define what is needed for ports, persistent volumes, credentials, upstream linking, and SSL integration to consider the template complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100