Deployment

The web client is optional, but when enabled it typically sits behind a proxy that serves static assets and forwards API/WebSocket traffic to moor-web-host.

Typical Topology

Browser → nginx (or other proxy) → moor-web-host → moor-daemon
            ↓
      Static assets
      (HTML/CSS/JS)

1. Browser loads static web client assets (HTML/CSS/JS) from the proxy
2. The proxy forwards /api, /auth, /fb, and /ws traffic to moor-web-host
3. moor-web-host connects to the daemon over RPC and relays FlatBuffer events to the client

Deployment Options

Docker Compose (Recommended)

The simplest way to deploy is using the provided Docker Compose configurations:

# Basic HTTP deployment
docker compose -f deploy/web-basic/docker-compose.yml up -d

# HTTPS with Let's Encrypt
docker compose -f deploy/web-ssl/docker-compose.yml up -d

Debian Packages

For Debian/Ubuntu systems, install the packages and configure nginx:

# Install from APT repository (recommended)
sudo apt install moor-daemon moor-web-host moor-web-client

# Or install from downloaded .deb files
sudo dpkg -i moor-daemon_*.deb moor-web-host_*.deb moor-web-client_*.deb

# Configure nginx (copy from deploy/debian-packages/)
sudo cp nginx-for-debian.conf /etc/nginx/sites-available/moor
sudo ln -s /etc/nginx/sites-available/moor /etc/nginx/sites-enabled/
sudo nginx -t && sudo systemctl reload nginx

Web client files are installed to /usr/share/moor/web-client/.

Kubernetes

See deploy/kubernetes/ for Ingress and Deployment manifests.

Proxy Configuration

Required Routes

The proxy must forward these paths to moor-web-host:

All other paths serve static web client assets.

Minimal nginx Configuration

upstream moor_api {
    server moor-web-host:8081;
}

server {
    listen 80;
    server_name your-moo.example.com;

    # Static files
    root /var/www/moor;
    index index.html;

    # SPA fallback
    location / {
        try_files $uri $uri/ /index.html;
    }

    # API routes
    location /api/ {
        proxy_pass http://moor_api;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
    }

    location /auth/ {
        proxy_pass http://moor_api;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
    }

    location /fb/ {
        proxy_pass http://moor_api;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
    }

    # WebSocket
    location /ws/ {
        proxy_pass http://moor_api;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_read_timeout 3600s;
    }
}

HTTPS Configuration

For production, use HTTPS. See deploy/web-ssl/nginx-ssl.conf for a complete example with:

• TLS termination
• HTTP to HTTPS redirect
• Let's Encrypt certificate renewal
• Security headers

WebSocket Timeouts

WebSocket connections are long-lived. Configure appropriate timeouts:

proxy_read_timeout 3600s;  # 1 hour
proxy_send_timeout 3600s;

Development Setup

During development, Vite serves the web client and proxies API/WebSocket requests:

# Terminal 1: Start daemon
npm run daemon:dev

# Terminal 2: Start web host
npm run web-host:dev

# Terminal 3: Start Vite dev server
npm run dev

Or use the combined script:

npm run full:dev

Vite's proxy configuration is in vite.config.ts.

Environment Variables

The web client reads these at build time:

Static Asset Hosting

The web client build produces static files in dist/:

• index.html - Main entry point
• assets/ - JavaScript, CSS, images

These can be served from any static hosting (nginx, S3, CDN, etc.). The only requirement is SPA-style routing: all non-asset requests should return index.html.

Health Checks

For load balancers and orchestrators:

Related Docs

• Server Architecture
• Running a mooR Server
• Server Configuration