FerryDocs
GuidesMultiple servers

Run a second server

Give the second server its own data directory, name prefix, addresses and base domain.

Edit on GitHub
Terminal
# production (defaults: prefix ferry, API :7878, proxy :8080)
ferryd --data-dir /var/lib/ferry

# staging, on the same Docker daemon
ferryd --data-dir /var/lib/ferry-staging \
  --name-prefix staging \
  --api-addr 127.0.0.1:7879 \
  --proxy-addr 0.0.0.0:8081 \
  --base-domain staging.localhost

Each server must have its own

WhatOptionWhy
--data-dirIts database, logs and certificates. The server that uses a data directory locks it.
--name-prefixEach Docker resource of the server has it. It must be unique for each daemon.
API address--api-addrTwo servers cannot listen on the same port.
Proxy addresses--proxy-addr, --https-addrThe same cause. Only one server can own ports 80 and 443.
--base-domainThen their apps do not answer to the same hostnames.

After the start

  • Account. Each server has its own account, sessions and API tokens, in its own data directory. At its first start, the staging server prints its own Create your account link, at its own API address: http://127.0.0.1:7879/setup?code=….
  • Apps. The apps of the staging server are at http://<name>.staging.localhost:8081.
  • Stop, status, logs. ferryd stop, ferryd status and ferryd logs act on the server of the data directory that you name.
Terminal
ferryd stop --data-dir /var/lib/ferry-staging

This command stops staging and does not touch production.

Multiple servers

Two or more Ferry servers can share one Docker daemon. Each has its own data, prefix and ports.

Choose the server in the CLI

The CLI saves one server. Flags or environment variables send one command to another server.

On this page

Each server must have its ownAfter the start