Expand multi-server docs, especially networking?

[crrobinson14]

I'd be happy to help contribute documentation on what I'm about to ask (I write quite a bit for a living), but need some guidance first on the most current/recommended way to communicate between two servers. Suppose you have Postgres on server A and an app on server B? What's the easiest/fastest/most bulletproof "Coolify way" to set this up?

Cloudflare tunnels are an option but the documentation seems to mostly focus on getting remote access e.g. to a server on a home or private LAN that you want to get to elsewhere. The docs don't really cover server-to-server comms.

Traefik as a proxy can do all kinds of wonderful things but at least IMO it's a more advanced concept for most. I'm not sure this is the best place for a newbie to start...

Obviously you have SaaS options like if you're in AWS cloud, you have the usual VPC mechanisms you would have with any other app. But they're vendor-specific and don't apply to all the cases where you can use Coolify.

Tailscale is an interesting option - it's really easy to set up, and addresses both server-to-server and admin-workstation-to-server needs. But it's not mentioned anywhere in the docs yet, so I'm not sure if it's really what the core maintainers want to recommend.

Ideally, what I'd like to achieve (and be happy to help document) is the simplest path to:

1. Set up Coolify on two servers.
2. Deploy app on A and postgres on B.
3. Add XYZ config, resource, or extra package and allow A to securely find and connect to B, a-la AWS Service Discovery, the way Docker Compose "services" work, or similar.

Any input would be appreciated. Thanks!

[crrobinson14]

Just trying to keep this alive, it looks like the Docker Swarm option plus Cloudflare tunnels might be the best way to start for a lot of cases? It's not trivial to set up but...

[veritymedia]

Would not having them on a private network (provided by the hosting provider) be the easiest? Or if running services in a manged cluster then docker can handle that as well, again, on the private network.

Given that Coolify is sponsored by Hetzner and Hetzner has a one click Coolify deploy when buying a server, maybe using Hetz networks is ideal?

[crrobinson14]

My question is specifically about cross-cloud deployments, where cloud-vendor-provided networking can't address this internally. That's why I mentioned Cloudflare tunnels and Tailscale. This is not uniquely a Coolify-oriented problem, but it is a very common task/challenge faced by the kinds of folks that might want to USE Coolify.

I'm not posting here asking for a solution (I'm currently doing this with Tailscale myself). I was hoping/offering to contribute to the documentation, and looking for input on what folks think is the best/most canonical "Coolify way" to do this. There's some information in the docs already on using Docker Swarm, but it's more of an overview (the Storage section just says "WIP").