Runbooks
Step-by-step operational procedures for BWD infrastructure.
All runbooks require HITL approval before execution unless marked Automated.
Chain Operations
| Procedure | Description | Automated |
|---|---|---|
| Add rpcallowip for VRSCTEST | Add Docker network subnet to vRSCTEST RPC allow list | No |
| Restart a chain | Graceful stop + start for any chain | No |
| Check sync status | Verify chain is fully synced | No |
| Clean chainstate | Wipe chainstate for fresh resync | No |
Deployment
| Procedure | Description | Automated |
|---|---|---|
| Deploy RPC Server on VRSCTEST | Build and deploy Rust RPC server on VRSCTEST testnet | No |
| Deploy QRcodes on VRSCTEST | Build and deploy QRcode creator on VRSCTEST testnet | No |
| Deploy idcreate on VRSCTEST | Build and deploy Verus identity creation service on VRSCTEST testnet | No |
| Deploy idcreate on VRSC | Build and deploy Verus identity creation service on VRSC mainnet | No |
| Deploy RPC Server | Build and deploy Rust RPC server (VRSC mainnet) | No |
| Deploy RVT SPA | Deploy RVT single-page app | No |
Conventions
Operational standards and patterns for all playbooks and runbooks:
| Convention | Description |
|---|---|
| Caddyfile management | Host file edits + validate/reload (no docker cp, no fmt inside container) |
| Route idempotency checks | Use grep -Fq for exact-domain matching |
| Variable scoping | Chain-prefixed vars (idcreate_vrsc_*) vs shared defaults |
| Docker network routing | PBaaS chains isolated by network; Caddy must be multi-homed |
| Compose project naming | Use COMPOSE_PROJECT_NAME env var, not hardcoded container_name |
Emergency
| Procedure | Description | Automated |
|---|---|---|
| Container failed to start | Debug and recover a crashed container | No |