Description
There's a single .env.example covering all environments. As Soroban config (network, RPC URL, contract ids) and the signing-key config from issue #16 grow, a single generic example makes it easy to accidentally point a testnet-configured local setup at mainnet contract ids by mistake.
Requirements and context
- Add
.env.testnet.example and .env.mainnet.example variants with correct, distinct defaults for each, and update the README's setup instructions to reference the right one
Suggested execution
- Fork the repo and create a branch
git checkout -b dx/env-example-variants
- Implement changes
Relevant files:
.env.testnet.example
.env.mainnet.example
README.md
-
Test and commit
- Run
npm run lint && npm run typecheck && npm test && npm run test:e2e
- Include test output / screenshots or logs demonstrating the fix in the PR
Example commit message:
feat: add environment-specific .env.example variants
Guidelines
- Assignment required before starting — comment to claim this issue
- PR description must include:
Closes #[this issue's number]
- Timeframe: 96 hours from assignment
- Complexity: High (200 points)
Part of the Drips Wave for vortex-backend.
Description
There's a single
.env.examplecovering all environments. As Soroban config (network, RPC URL, contract ids) and the signing-key config from issue #16 grow, a single generic example makes it easy to accidentally point a testnet-configured local setup at mainnet contract ids by mistake.Requirements and context
.env.testnet.exampleand.env.mainnet.examplevariants with correct, distinct defaults for each, and update the README's setup instructions to reference the right oneSuggested execution
Relevant files:
.env.testnet.example.env.mainnet.exampleREADME.mdTest and commit
npm run lint && npm run typecheck && npm test && npm run test:e2eExample commit message:
Guidelines
Closes #[this issue's number]Part of the Drips Wave for vortex-backend.