FerryDocs
Architecture

Networking model

Containers talk to each other on a private network, and the outside reaches them only through the proxy.

Edit on GitHub
Docker bridge network: ferry127.0.0.1:63114BrowserProxyon the hostweb127.0.0.1:49321web127.0.0.1:49322apiprivate, port 8000app-dbPostgres, 5432psqlon the host

A browser reaches a public service only through the proxy, on port 80 or 443.

1 / 4

Ferry uses two kinds of connections:

  • Containers talk to each other on a private Docker network.
  • The outside reaches the public services only through the in .

The two ends of the proxy stay on the host. It listens on the public addresses that you choose. It connects to the containers through ports on 127.0.0.1.

For the user view, see Networking and domains.

In this section

The private networkOne bridge network, with a name for each container.Published portsHow the proxy reaches a container.Hostnames and routingWhich hostname goes to which service.HTTPSHow certificates come and go.

What it never does

The reconciler changes only the containers of this server, never settings, volumes or other servers.

The private network

Each server makes one Docker bridge network where each container has a name.

On this page

In this section