How to self-host

Run your own Tusile community server with Docker. The bundle includes Caddy for HTTPS and LiveKit WebSocket. Download, set a few variables, edit the Caddyfile with your domain, and start the stack.

1. Unpack the archive (e.g. unzip community-server.zip and cd community-server).
2. In the unpacked folder, set these in .env (copy from .env.example if present):
   • SERVER_TOKEN — token from the Tusile Core Server to register your community.
   • HOSTNAME — public URL of your server with no path (e.g. https://chat.example.com). Must match the domain in the Caddyfile.
3. Edit Caddyfile: replace community.example.com with your domain. Caddy will obtain TLS certificates automatically.
4. Start the stack:

   docker compose up -d

NAT / firewall ports

Open these ports on your router or firewall so the server and voice/video work from the internet:

• Caddy (HTTPS + LiveKit WSS): 80/tcp, 443/tcp, 7880/tcp. Caddy serves the community API on 80/443 and LiveKit WebSocket on 7880.
• LiveKit (voice/video):
  • 7881/tcp — RTC fallback.
  • 50000–50060/udp — RTP media. Must be reachable for voice/video.

Port 9090 is also exposed for direct access to the community API if needed; with Caddy, 80/443 are the main entry.

After the containers are up and ports are open, your community server and LiveKit (voice/video) will be running. You should now be able to connect to your server in the Tusile app.