Installation guide

The image on a Linux server

Build the image, prepare the server and start the container on your domain.

Building the image

The image is built on the development machine, with Docker Desktop running Linux containers, and travels to the server as a file: the server needs no registry and no source code.

  1. From the root of the repository, run .\rebuild_container_release.ps1 -NoSeedData: it builds the image, checks that it holds no source and every compiled part, starts it for a trial and saves it as deploy\docker\merydion-allinone.tar with its fingerprint.
  2. Copy the image and its fingerprint to the server, for example with scp deploy/docker/merydion-allinone.tar* admin@merydion.example.com:/tmp/.
  3. On the server, check the fingerprint and load the image: cd /tmp && sha256sum -c merydion-allinone.tar.sha256 && docker load -i merydion-allinone.tar.

Tip Without -NoSeedData the build also packs merydion-data.tar.gz with the development machine's data — personal data and the private key of the sign-in service included: it is not for a new installation.

Preparing the server

On the server, keep the layout of the repository: the compose file finds its neighbours by relative path. The files below belong to the server, never to the image.

  1. Point the DNS record of your domain at the server and open ports 80 and 443 to the Internet.
  2. In deploy/prod-allinone/Caddyfile, write a real email in the global block: Let's Encrypt writes to it before a certificate expires.
  3. Create deploy/prod-allinone/.env with MERYDION_DOMAIN=merydion.example.com and, so that the verification emails leave, MERYDION_AUTH_SMTP_PASSWORD= followed by the password of the mailbox.
  4. Create SERVER_SECRETS.json at the root of the repository, readable only by you (chmod 600): the other secrets of the services go there, and with none it holds { "services": {} } — without the file the container does not start.
  5. Write your email in ADMINISTRATORS, at the root of the repository.

Tip A secret never goes in SERVER_CONFIGURATION.json, which is versioned and keeps the secret fields empty; the variable of a field wins over SERVER_SECRETS.json.

Starting the container

The container holds the gateway, the services, the portal and the apps. It starts from the loaded image, without building anything on the server.

  1. From the root of the repository: docker compose --env-file deploy/prod-allinone/.env -f deploy/prod-allinone/docker-compose.yml up -d.
  2. Check that it runs: docker compose -f deploy/prod-allinone/docker-compose.yml ps must say running, not restarting.
  3. On the first visit Caddy obtains the certificate, which takes up to a minute: curl -sS https://merydion.example.com/health then answers ok.
  4. If the container keeps restarting, a service has stopped and taken the others with it: read why with docker compose -f deploy/prod-allinone/docker-compose.yml logs --tail=80.

Tip Video calls on this server also need the UDP port of the media service and a TURN relay: the single-node runbook in the repository describes the extra settings.

Back to the guide

Productivity, made in Italy.

Bring the whole suite to your team — simple, secure and entirely yours.