Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to Connect to External PostgreSQL and Redis Clusters #919

Open
mcandylab opened this issue Dec 17, 2024 · 0 comments
Open

Ability to Connect to External PostgreSQL and Redis Clusters #919

mcandylab opened this issue Dec 17, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@mcandylab
Copy link

What problem will this feature address?

Currently, Dokploy seems limited to deploying and managing its own PostgreSQL and Redis instances. For users who already rely on externally managed database clusters (e.g., PostgreSQL and Redis) provided by their cloud providers—complete with built-in high availability, backups, and ongoing maintenance—it’s challenging to integrate these resources with Dokploy. As a result, they cannot leverage their existing fault-tolerant infrastructure and must settle for local instances that may not meet their redundancy and reliability needs.

Describe the solution you'd like

I would like Dokploy to support configuring and connecting to externally managed PostgreSQL and Redis clusters. This means providing a straightforward configuration method (e.g., environment variables, configuration files, or UI fields) where users can specify connection details (host, port, credentials, SSL settings) for their existing database and cache clusters. Dokploy should then seamlessly interact with these external services as if they were its own managed resources.

Describe alternatives you've considered

Local Deployments:
Running PostgreSQL and Redis locally within the Dokploy environment, but this compromises high availability and ease of maintenance.

Custom Integration Scripts:
Writing custom scripts or proxy services outside of Dokploy to route traffic to the external databases. However, this increases complexity and reduces the benefits of a single integrated solution.

Forking/Modifying Dokploy Code:
Making code changes to Dokploy to hardcode external connections, but this is not sustainable for future updates or for non-technical users.

Additional context

By enabling direct connections to managed clusters, Dokploy can become more versatile in enterprise settings where externally provisioned, fully managed services are standard. This integration would improve resilience, reduce operational overhead for users, and ultimately help Dokploy fit into more complex infrastructure scenarios.

Will you send a PR to implement it?

No

@mcandylab mcandylab added the enhancement New feature or request label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant