Render and Demo Account Pipeline

Render Blueprint

Durabull Cloud uses a Render blueprint (maintained with the deployment; not always present in the public repository). Typical services:

• durabull web service
• demo-redis managed Redis (Render KV)
• seed-demo-account cron job (every 12 hours)

MCP on Durabull Cloud

The durabull web service exposes MCP on the same hostname and port as the API and web UI:

https://<your-app-domain>/mcp

There is no separate Render service or MCP port. Set APP_BASE_URL on the web service to the public HTTPS origin (for example https://app.durabull.io) so OAuth resource metadata advertises {APP_BASE_URL}/mcp.

Post-deploy: MCP operations runbook. Run mcp:e2e on staging only when validating auth changes — it registers OAuth clients and writes tokens to the database.

Demo Refresh Pipeline

The cron job:

• reads DURABULL_DEMO_ACCOUNT_REDIS_CONNECTION_STRING
• flushes the demo Redis database
• reseeds realistic queues/jobs/scheduled jobs/redis keys
• writes health metadata keys

Reference:

• tooling/scripts/seed-demo-account.ts (cron invokes this script; see file header for DURABULL_DEMO_ACCOUNT_REDIS_CONNECTION_STRING)

Demo Health Keys

• durabull:demo:seed-metadata
• durabull:demo:last-seeded

These can be checked from Redis CLI or monitoring scripts.

Manual Verification Steps

1. Trigger seed-demo-account run from Render dashboard.
2. Confirm successful run logs.
3. Open Durabull using demo connection.
4. Verify queues, delayed jobs, and scheduled jobs appear fresh.

Important Safety Rule

The demo Redis instance is intentionally wiped every cycle.

• Do not store production data in this instance.

Screenshot placeholder: Render service overview and cron run logs.

Video placeholder: end-to-end demo reseed verification.