FerryDocs
Concepts

Networking, domains & TLS

One proxy receives the public traffic. Behind it, your services call each other on a private network.

Edit on GitHub
Private networkapi:3000app-db:5432BrowserDNSname → addressProxythe public sideshopweb serviceapiprivate serviceapp-dbdatastore

The browser asks DNS for the address of shop.example.com.

1 / 4

Each Ferry server runs one . The proxy receives all the public traffic and sends each request to a of the correct .

Behind the proxy, all the containers of the server share a . There, they call each other by name.

See your domains

Terminal
ferry domains        # the domains of the server and their status
ferry certificates   # each hostname and the state of its certificate

In this section

Public URLsWhich services get a URL, and how Ferry makes it.How the proxy routesFrom the Host header to an instance, in six steps.Private networkServices call each other by name.Automatic HTTPSFerry gets a certificate for each hostname.

Limits

A build has four limits. They are about uploads, registries, submodules and the CPU architecture.

Public URLs

Web services and static sites answer at one public URL under each domain of the server.

On this page

See your domainsIn this section