hoox infra command group.
This guide is your operations manual for provisioning, inspecting, and managing Hoox edge infrastructure.
⚡ 1. One-Click Quick Provisioning
When setting up your trading workspace for the first time, you do not need to manually configure resources in Cloudflare’s dashboard. The Hoox CLI automatically parses your enabled workers’ configurations and spins up the entire infrastructure stack in one command:- D1 SQLite Database (
hoox-db). - CONFIG_KV Namespace bucket.
- messaging Queue.
- andR2 object storage buckets.
- Vectorize vector search database.
🗄️ 2. D1 Database Administration
D1 databases store your critical transactional data (ledger, positions, balance history).Once a D1 database is created, the CLI will output its unique
database_id (a
36-character UUID). You must ensure this ID is bound in your worker’s
wrangler.jsonc file so the worker V8 isolate can establish a connection at
runtime.🔑 3. KV Configuration Namespace Management
KV stores are used to manage fast-path configurations, global parameters, and the kill switch.📨 4. Asynchronous Queues Setup
Queues guarantee order delivery during periods of extreme exchange rate limits or network congestion.Queue Parameters & Throttling
During provisioning, Hoox configures the queue with:- Retry Backoff: 30 seconds initial delay, scaling exponentially up to 15 minutes.
- Message Retention: 4 days (ensuring messages are preserved even during prolonged exchange maintenance events).
📦 5. R2 Object Storage Administration
R2 is an S3-compatible, zero-egress fee object storage service used to offload heavy JSON payloads and PDF portfolio reports.🧠 6. Vectorize RAG Index Management
Vectorize indexes house high-dimensional vector embeddings that power semantic search and Telegram AI bot memory.🔗 Next Steps
- Database Migrations & SQL — Run queries, manage drizzle schemas, and restore backups.
- Take-to-Production Deployments — Deploy your compiled workers and bind V8 isolates globally.