Alternative Installation Methods

While Docker Compose is the recommended approach for most users, mooR provides several other installation methods for different use cases and environments.

Debian Packages

For Debian-based systems (including Ubuntu), mooR provides pre-built packages that integrate cleanly with your system's package management.

About Debian Packages

The Debian packages are built from the debian directory in various mooR repositories and are available on the releases page of the mooR GitHub repository. These packages handle:

• Installing binaries in standard system locations
• Setting up system services and users
• Managing dependencies automatically
• Providing standard Debian package management integration

Installation Process

1. Download the packages from the mooR GitHub releases page
2. Install using your package manager:

   sudo dpkg -i moor-*.deb
   sudo apt-get install -f  # Install any missing dependencies
   

3. Configure your core database (see Understanding MOO Cores)
4. Start the services using systemd or your preferred service manager

When to Use Debian Packages

Debian packages are ideal when:

• You're running a Debian-based Linux distribution
• You want system-level integration (systemd services, standard file locations)
• You prefer traditional package management
• You're setting up a production server on bare metal or VPS

Building from Source

For developers, custom deployments, or platforms without pre-built packages, you can compile mooR from source code.

Prerequisites

You'll need the Rust toolchain installed. The recommended way is using rustup:

# Install rustup (if not already installed)
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

# Follow the installation prompts, then restart your shell or run:
source ~/.cargo/env

Building Process

1. Clone the repository:

   git clone https://github.com/rdaum/moor.git
   cd moor
   

2. Build all components:

   cargo build --release --all-targets
   

   This will take some time as Rust compiles all dependencies and mooR components.

3. Find your binaries: After building, you'll find the executables in target/release/:

   • moor-daemon
   • moor-telnet-host
   • moor-web-host
   • curl-worker

Manual Configuration

When building from source, you'll need to manually set up:

• Authentication keys: Generate moor-signing-key.pem and moor-verifying-key.pem
• Configuration files: Create appropriate configuration for each component
• Core database: Install and configure your chosen MOO core
• Service coordination: Ensure all components can communicate properly

The docker-compose.yml file provides excellent examples of how to configure each component.

When to Build from Source

Source builds are best for:

• Development and testing
• Platforms without Debian package support
• Custom configurations requiring code modifications
• Learning how mooR works internally
• Contributing to the project

Configuration Reference

Regardless of your installation method, you'll need to configure mooR's components. The arguments and options for the server executables are documented in the Server Configuration chapter.

Choosing Your Method

Getting Help

For installation issues:

• Check the mooR GitHub repository for the latest installation instructions
• Review the docker-compose.yml file for configuration examples
• Consult the community forums or Discord for platform-specific guidance

Remember that regardless of your installation method, you'll also need to choose and install a MOO core database - see Understanding MOO Cores for guidance on that crucial next step.