Installation
Installation Guide
Section titled “Installation Guide”Prerequisites
Section titled “Prerequisites”- Rust 1.70+ with cargo
- Docker for the local stack
- OpenSSL development libraries
- Node.js 22.12+ for the
docs/siteworkspace
Build from Source
Section titled “Build from Source”1. Clone the repository
Section titled “1. Clone the repository”git clone https://github.com/southwest-ai-labs/xavier.gitcd xavier2. Build the project
Section titled “2. Build the project”# Debug buildcargo build
# Main runtime binarycargo build --bin xavier3. Run validation
Section titled “3. Run validation”cargo test --workspace --features ci-safe --exclude xavier-webnpm run build --workspace panel-uinpm run build --workspace docs/siteConfiguration
Section titled “Configuration”Runtime configuration
Section titled “Runtime configuration”Xavier now treats config/xavier.config.json as the canonical location for non-secret runtime settings. Secrets and credentials belong in .env.
Environment variables
Section titled “Environment variables”| Variable | Default | Description |
|---|---|---|
XAVIER_TOKEN |
no safe default | API authentication token |
XAVIER_CONFIG_PATH |
config/xavier.config.json |
Optional override for the canonical runtime config file |
| provider API keys | unset | External API credentials |
The current server still contains environment-based code paths internally, but the repository standard is now:
config/xavier.config.jsonfor non-secret operational settings.envfor credentials and secrets
Running Xavier
Section titled “Running Xavier”Development mode
Section titled “Development mode”cargo run --bin xavierRelease binary
Section titled “Release binary”cargo build --release --bin xavier./target/release/xavierDocker
Section titled “Docker”cp .env.example .envdocker compose build xavierdocker compose up -dVerify Installation
Section titled “Verify Installation”curl http://localhost:8003/healthcurl http://localhost:8003/readinessStorage Reality
Section titled “Storage Reality”- The current validated deployment uses
FileMemoryStore. - SurrealDB is present in the repo and Docker setup, but it is not the default validated backend for current production-style documentation.
- If you need broader hosted persistence work, treat SurrealDB as an explicit follow-up track rather than an assumed default.