Skip to main content

Choose a Deployment Path

Flo deployments are managed with Docker. Choose the procedure based on the number of tenants and who operates the infrastructure.

One instance managed directly​

Use Single-tenant deployment to install one instance with compose.yaml, PostgreSQL 17, Flo, and Nginx. The procedure uses .env.example and the deploy.sh script.

Multiple instances managed with the Flo CLI​

For a multi-tenant fleet, use Multi-tenant deployment with the CLI. The CLI manages the tenant registry, VPSs, configuration, blue-green deployments, and backups. Do not run the single-tenant procedure on a host managed by the CLI.

Before deployment​

  1. Choose the topology: single-tenant or multi-tenant.
  2. Prepare the domain and DNS, SSH access, and an account with the required server permissions.
  3. Configure required values using Environment Variables; do not invent variables by copying old .env files.
  4. Configure TLS and the proxy for the chosen topology. For multi-tenant deployments, DNS, TLS, and routing are managed through the CLI and Traefik.
  5. After startup, check container status, logs, and the application's /health endpoint.

Operational references​

This page replaces the old manual procedure: do not install a separate database or manually create certificates and Nginx paths by following outdated instructions. The two supported paths are described in the deployment guides linked above.