Document the supported local development stack for frontend contributors

[priscaenoch]

Problem

docker-compose.yml defines three parallel network stacks (db-testnet/api-testnet/indexer-testnet, and the same for mainnet and devnet) plus redis. A contributor who only wants to run the explorer locally has no guidance on which subset of these services to start, which ports they expose, or which environment variables must be set for each.

Combined with the service-name mismatch against the frontend's nginx proxy, getting a working local stack currently requires reading docker-compose.yml and the frontend's nginx configuration side by side.

What needs to be done

• Document a single supported "run the explorer locally" path: the exact compose command/profile, the services it starts, the ports, and the required environment variables.
• Consider adding compose profiles so docker compose --profile testnet up starts only the testnet stack.
• State clearly which service the frontend must point at (:3001) and cross-link the frontend repository's setup instructions.
• Verify the documented path works from a clean checkout.

Files

• docker-compose.yml
• README.md
• .env.example

Acceptance deliverables

• A documented, verified command brings up a working local backend for the frontend.
• Ports, services, and required variables are listed.

Tests to pass

• Documented verification from a clean checkout: the stack starts and /health on the indexer responds.

[AnnieIj]

Hi! I'd love to work on this issue.

I plan to document the supported local development stack for frontend contributors, including the required tools, dependencies, environment setup, installation steps, and common troubleshooting tips. I'll ensure the documentation is clear, easy to follow, consistent with the project's structure, and helps new contributors get up and running quickly. Could you please assign this issue to me?

[grantfox-oss]

🦊 GrantFox — @NUMBER72857 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #25)
2. Your PR will be reviewed by the octraban maintainers

Good luck! Track your progress on GrantFox.