Dokploy / Dokploy/dokploy

Feedback and Development Suggestions for Dokploy Platform

Open
#1,915 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

What problem will this feature address?

While https://dokploy.com/ offers many advantages across various aspects, I frequently encounter port-related issues during implementation. One of the most common problems is receiving "Bad Gateway" errors due to port conflicts.

Suggestion: Implement a port visualization feature that would display currently used ports across the platform. This would provide users with:

  • A clear overview of occupied ports
  • The ability to identify conflicts before they occur
  • Options to select available ports when deploying new services

Limited Mail Server Templates

There appears to be very few (or possibly no) ready-to-use templates for mail servers in the platform. This significantly increases setup time and complexity for users.

Suggestion: Expand the template library to include:

  • A comprehensive selection of mail server configurations
  • Pre-configured Mailcow deployment templates
  • Options for popular alternatives like Postfix/Dovecot combinations
  • Support for webmail interfaces with various security configurations
Describe the solution you'd like

Docker Implementation Problems with Mailcow

I've attempted multiple installations of https://github.com/mailcow/mailcow-dockerized using Docker, but consistently face connection errors or incomplete installations. The deployment process seems to encounter compatibility issues within the Dokploy environment.

Suggestion: Develop specific integration guidelines or automated deployment scripts for popular open-source solutions like Mailcow that are optimized for the Dokploy platform.

Describe alternatives you've considered

Limited Mail Server Templates
There appears to be very few (or possibly no) ready-to-use templates for mail servers in the platform. This significantly increases setup time and complexity for users.

Suggestion: Expand the template library to include:

  • A comprehensive selection of mail server configurations
  • Pre-configured Mailcow deployment templates
  • Options for popular alternatives like Postfix/Dovecot combinations
  • Support for webmail interfaces with various security configurations
Additional context

No response

Will you send a PR to implement it?

No

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. The request combines port visualization, mail-server templates, and Mailcow deployment integration, so the relevant implementation area and acceptance criteria would need to be established before work begins.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, typescript
Domain
devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.