RMI Deployment 🟢

Production deployment of rmi-backend (FastAPI + Uvicorn).

Docker (recommended)

git clone https://git.rugmunch.io/RugMunchMedia/rmi-backend.git
cd rmi-backend
cp .env.example .env   # edit: DATABASE_URL, REDIS_URL, API keys for data providers
docker compose up -d --build

The compose stack starts:

Service	Port	Purpose
rmi-backend	8000	FastAPI application (Uvicorn workers)
postgres	5432	Primary store (scans, wallets, users)
redis	6379	Cache + rate-limit counters + task queue
qdrant	6333	Vector KB (security patterns, RAG)

Reverse proxy

server {
    listen 443 ssl http2;
    server_name api.example.com;

    # ssl_certificate / ssl_certificate_key: Let's Encrypt

    location / {
        proxy_pass http://127.0.0.1:8000;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto https;
        limit_req zone=api burst=20 nodelay;
    }
}

Health checks

curl https://api.example.com/healthz      # liveness
curl https://api.example.com/readyz       # DB + Redis connectivity

Data provider keys

RMI enriches scans with free-tier data APIs (price, liquidity, holder analysis). All are optional — the scanner degrades gracefully without them, reporting which checks were skipped. Add keys to .env as you go:

• COINGECKO_API_KEY, DEXSCREENER_* — market data
• HELIUS_API_KEY — Solana RPC + webhooks
• ALCHEMY_API_KEY — EVM RPC
• BIRDEYE_API_KEY — Solana token analytics

Upgrade procedure

1. git pull the tag you're deploying.
2. docker compose pull && docker compose up -d --build (schema migrations run on boot via Alembic).
3. Verify GET /healthz and re-run one known token scan to compare output shape.
4. Keep the previous image tag for 48 h for rollback: docker compose up -d --build against the old tag.