This guide explains how to deploy Bedrud to a production server.

Deployment Options

Package Manager

Install Bedrud on Debian/Ubuntu or Arch Linux using the native package manager. This is the recommended method for persistent server deployments where you want automatic updates via apt upgrade or the AUR.

See the Package Installation guide for full instructions, including adding the apt GPG key and repository.

# Ubuntu / Debian
sudo apt install bedrud
 
# Arch Linux (AUR)
yay -S bedrud-bin

After installation, run the interactive installer to configure TLS, systemd services, and the database:

sudo bedrud install

Automated CLI Deployment

The fastest way to deploy. Run from your local machine:

Prerequisites: Python 3.10+, uv, and SSH access to the target server.

cd tools/cli
uv run python bedrud.py --auto-config \
  --ip <server-ip> \
  --user root \
  --auth-key ~/.ssh/id_rsa \
  --domain meet.example.com \
  --acme-email admin@example.com

This will:

1. Build the backend binary locally
2. Compress and upload it via rsync
3. Clear conflicting web servers
4. Configure the firewall
5. Install and start services on the server

CLI Options

Manual Installation

1. Build the Binary

make build-dist

This produces dist/bedrud_linux_amd64.tar.xz.

2. Upload to Server

scp dist/bedrud_linux_amd64.tar.xz root@server:/tmp/
ssh root@server "cd /tmp && tar xf bedrud_linux_amd64.tar.xz"

3. Install

ssh root@server
sudo /tmp/bedrud install --tls --domain meet.example.com --email admin@example.com

See the Installation Guide for all installation scenarios.

4. Create Admin User

			
sudo ./bedrud user promote --email admin@example.com
		

Docker Deployment

Build and run with Docker:

docker build -t bedrud .
docker run -d --name bedrud -p 8090:8090 -p 7880:7880 -v bedrud-data:/var/lib/bedrud bedrud

A pre-built image is also available:

docker pull ghcr.io/bedrud-ir/bedrud:latest

See the Docker Guide for full details including volumes, configuration, and Docker Compose.

Production Architecture

flowchart TB
    NET[Internet] --> TRAEFIK["Traefik (443)<br/>TLS termination, reverse proxy"]
    TRAEFIK --> BEDRUD["Bedrud (8090)<br/>API + Web UI"]
    TRAEFIK --> LIVEKIT["LiveKit (7880)<br/>WebRTC media"]
    BEDRUD --> DB["SQLite<br/>(or PostgreSQL)"]

For WebRTC connectivity, also open these ports on the firewall:

See WebRTC Connectivity for the full connectivity stack.

Managing Services

# Check status
systemctl status bedrud livekit
 
# Restart
systemctl restart bedrud
 
# View logs
journalctl -u bedrud -f
tail -f /var/log/bedrud/bedrud.log

File Locations (Production)

CI/CD

Release Pipeline

The release.yml workflow triggers on version tags (v*) and produces:

All artifacts are attached to the GitHub release.

Nightly Builds

The dev-nightly.yml workflow produces development builds on a schedule.

CI Checks

Every push to main and every pull request runs: