Docker services
| Service | What it runs | Port on the machine | Purpose |
|---|---|---|---|
api |
auratree-api |
3040 (127.0.0.1 by default) | API and web client |
postgres |
auratree-postgres |
3041 (127.0.0.1) | Database |
redis |
Valkey 9 | 3042 (127.0.0.1) | Cache and sessions |
livekit |
LiveKit server | 7880 (127.0.0.1 by default), 7881/tcp, UDP 50000–50100 | Voice and video |
ntfy |
ntfy | 3048 (127.0.0.1) | Phone push notifications |
minio |
MinIO, frozen copy | 3043 S3, 3044 console (127.0.0.1) | File storage, only with the bundled MinIO |
coturn |
coturn | host network | TURN, only with the turn profile |
The cache service is still called redis, and its settings keep the Redis names. It runs Valkey, which speaks the same protocol.
What faces your users
Section titled “What faces your users”Only these, and only through your TLS reverse proxy:
- Your chat name, to the API on port 3040.
- Your voice name, to LiveKit on port 7880 (with WebSocket support).
- With the bundled MinIO only: a files name, to port 3043.
Plus, open directly: TCP 7881 and UDP 50000–50100 for voice media.
Everything else listens on 127.0.0.1 only. Ports that Docker publishes skip your firewall (ufw), which is why. Keep it that way if you change a port. If your proxy runs in another container or on another machine, set API_BIND and LIVEKIT_BIND to this machine’s LAN address.
Push notifications
Section titled “Push notifications”- Phones use ntfy. It ships locked down: create its admin user and token once, as in Deploy AuraTree. Push messages only carry a “wake up” signal, never message content.
- Browsers use Web Push. It’s on by default with no setup. Set
WEB_PUSH_ENABLED=falseto turn it off.
For members behind strict networks, start the extra coturn service:
docker compose --profile turn up -dIt needs TURN_SECRET, TURN_URLS and TURN_EXTERNAL_IP in .env, and its own ports open: 3478 (TCP and UDP) and UDP 49160–49200.
Resource limits
Section titled “Resource limits”Every service has a memory and process limit, so one that runs away is restarted instead of taking the machine down. On a big server, raise the *_MEM_LIMIT settings first.
