Self-Hosted Floe Operations

Common commands

docker compose logs -f                  # tail logs for all services
docker compose ps                       # check container status and health
docker compose down                     # stop and remove the stack
docker compose restart server           # restart only the signaling server

Update to the latest code

docker compose pull
docker compose up -d

That pulls the newest published images and restarts. Nothing is built locally, so there is no repository to keep in sync.

Changing NEXT_PUBLIC_SOCKET_URL needs only docker compose up -d; the client reads it at runtime. See How the Client Finds the Signaling Server. NEXT_PUBLIC_SITE_URL is the exception: it is written into the page at build time, so the published image omits those tags entirely rather than pointing them at somebody else’s domain. See Container Images if you want your own.

Health endpoints

The signaling server exposes two health endpoints you can use in load balancers or uptime monitors:

Endpoint	Purpose	Response
`GET /health`	Liveness check	`{ "status": "healthy", "uptime": <seconds> }`
`GET /`	Status and timestamp	`{ "status": "ok", "timestamp": "..." }`

⌘I

Getting Started

Web App

CLI

Self-Hosting

How It Works

Reference

Self-Hosted Floe Operations

Common commands

Update to the latest code

Health endpoints

​Common commands

​Update to the latest code

​Health endpoints

Common commands

Update to the latest code

Health endpoints