@genius-revius/server

Local coordinator server for Revius -- HTTP + WebSocket API with SQLite storage.

Install

npm install @genius-revius/server

Usage

import { createReviusServer } from "@genius-revius/server";

const server = await createReviusServer({ port: 7878 });

Typically launched via revius dev from @genius-revius/cli. See the main README for full documentation.

Cloud deployment (Railway, Fly, etc.)

The revius-coordinator binary (src/start.ts) is a standalone Fastify entry point for running the coordinator against a mounted data volume, without a per-project config. It binds 127.0.0.1 by default -- for a cloud deploy, set these env vars explicitly on the service:

HOST=0.0.0.0                  # required to accept traffic from the platform's proxy
REVIUS_AUTH_TOKEN=<random>     # required whenever HOST is non-loopback
REVIUS_DATA_DIR=/data          # or rely on auto-detection if /data is mounted

Notes:

• HOST always defaults to 127.0.0.1 (loopback-only). It is never widened unless you set it explicitly, or unless a /data volume is detected with REVIUS_DATA_DIR unset (common on Railway) -- in that case the coordinator auto-binds 0.0.0.0, but only if REVIUS_AUTH_TOKEN is set; otherwise it refuses to start.
• Prefer setting HOST=0.0.0.0 and REVIUS_AUTH_TOKEN explicitly in the Railway service variables rather than relying on the /data auto-detection -- it makes the cloud posture visible in the deploy config instead of implicit in a filesystem check.
• In NODE_ENV=production, app.ts additionally refuses to start on a non-loopback host without REVIUS_AUTH_TOKEN, as defense in depth.