Mainnet deployment guide (Render + UptimeRobot + Neon + external RPC)

[Miracle656]

Background

Once Wraith is network-aware, operators need a concrete runbook to stand up a mainnet instance. Mainnet has no free public Soroban RPC (an external provider endpoint is required), Render free web services sleep (needs an uptime pinger), and Render's free Postgres is deleted after 90 days (use an external Postgres).

What to build

A docs/DEPLOY_MAINNET.md covering the full stack and the env matrix — without committing any secret endpoint or key.

Key files

• docs/DEPLOY_MAINNET.md — new
• .env.example — align with the guide

Suggested execution

git checkout -b docs/mainnet-deploy-guide

1. Document env: STELLAR_NETWORK=mainnet, SOROBAN_RPC_URL (external provider — placeholder only, real value in host secrets), mainnet SAC CDLZFC3SY…, external DATABASE_URL
2. Render: keep-alive via UptimeRobot pinging /status every 5 min; note the 750 instance-hours/month free cap (~one always-on service)
3. DB: use Neon/managed Postgres (never Render free Postgres — 90-day deletion); link the backup workflow (W076)
4. Testnet vs mainnet run side-by-side (separate DBs)

Acceptance criteria

• Full env matrix for testnet + mainnet
• No secrets/keys committed — placeholders only
• Documents the RPC-provider requirement, Render sleep + hours cap, and DB durability
• Links the backup runbook

Drips Wave · Complexity: Easy · 100 points

---

Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk

[PetJs]

@PetJs has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer
I'd like to contribute to this project. Can I be assigned this issue?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @PetJs to this issue.

[tobiadewola41-eng]

@tobiadewola41-eng has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @tobiadewola41-eng to this issue.

[ibochielizabeth-spec]

@ibochielizabeth-spec has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’m interested in working on Issue #166 because having a clear deployment guide is important once Wraith supports multiple networks. Operators should be able to deploy a mainnet instance without having to figure out the infrastructure, environment variables, and service requirements from the source code.

I will create docs/DEPLOY_MAINNET.md with a complete deployment walkthrough covering Render, external Soroban RPC, Neon/managed PostgreSQL, and UptimeRobot. I will clearly separate testnet and mainnet configuration and document the required environment variables for each.

The guide will explain that mainnet requires an external Soroban RPC provider and will only use placeholders for provider URLs or credentials. No private keys, secret endpoints, or other sensitive information will be committed to the repository.

I will also document Render's free-tier limitations, including service sleeping and the monthly instance-hour limit, along with the recommended UptimeRobot configuration for periodically checking /status.

For database durability, I will recommend an external managed PostgreSQL provider such as Neon rather than Render's free PostgreSQL option. I will also link the existing backup and restore documentation so operators have a clear recovery path.

Finally, I will update .env.example where necessary so it matches the deployment guide and verify that the documented setup is complete, consistent, and practical for running testnet and mainnet side by side.

The goal is to provide a straightforward, secure deployment runbook that allows another operator to reproduce a Wraith mainnet deployment without relying on undocumented knowledge.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ibochielizabeth-spec to this issue.

[deshrajvermay9517-png]

@deshrajvermay9517-png has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi, I'd like to work on this. I'll create the mainnet deployment guide with a clear testnet/mainnet env matrix, external RPC setup, Render + UptimeRobot configuration, managed Postgres guidance, and the backup runbook reference. I'll also align .env.example and make sure no secrets are included. Please assign it to me if it's available.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @deshrajvermay9517-png to this issue.

[DevQwinB]

@DevQwinB has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Oh I am so excited about this one, documentation done right is genuinely underrated! Hi, I would like to work on this issue. I will write the full docs/DEPLOY_MAINNET.md covering the complete env matrix for both testnet and mainnet including STELLAR_NETWORK, SOROBAN_RPC_URL as a placeholder only, the mainnet SAC address, and an external DATABASE_URL, documenting the Render sleep behaviour and the 750 instance-hours monthly cap alongside the UptimeRobot keep-alive setup pinging /status every five minutes. I will make absolutely sure to call out the Neon or managed Postgres requirement over Render's free Postgres given the 90-day deletion risk, link the backup runbook, and align .env.example with everything the guide covers so operators have a complete and trustworthy reference with zero secrets committed anywhere. Can I be assigned?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @DevQwinB to this issue.