Multi-server feature about dokploy

[Siumauricio]

Hi @jocubeit ,

Docker swarm is specifically to manage multiple servers as nodes and scaling, you can build and deploy from the node manager and if you want you can also deploy an application to a specific node(server), however of course we have a single point of failure, so you would need more manager nodes to share traefik information and more things to have an abundance of nodes to prevent single point of entry failures and also the problem is that builds are executed on the manager node which can cause instability.

The multi server feature of coolify I don't know to what extent it allows manager nodes to overflow and recover from a failure in the main node.

According to the documentation they do not natively integrate docker swarm and it is experimental so I do not know to what extent you are referring to manage multiple servers and have redundancy and recover from failures that I think it does not handle it or maybe I'm wrong.

https://coolify.io/docs/knowledge-base/docker/swarm

It's almost the same term, the main point is to be able to deploy applications on a specific node or server, you can actually do that with docker swarm as we have it integrated.

If you could give me more details on how you think it should work/steps we could create/rethink a more complex functionality thought in server management and how it currently works coolify would be great!

Thanks!

[anbraten]

From what I understand instead of using one docker socket connected to the swarm master to manage apps, a first step would be to allow adding "nodes" using an additional docker socket. So basically dokploy would be able to manage multiple docker systems or even multiple docker swarms and if I understand OP correctly you could select "deploy to swarm1" where swarm1 would be a docker connection to a swarm or just a single docker server. Each swarm / node would provide its own Traefik etc if you select multiple servers (as in Coolify) it would deploy it to independet systems as if you would manually deploy to two dokploys, but instead both systems are sharing one UI / management system.