Add .env.example files for all components with documentation

[Smartdevs17]

Problem

Environment variable requirements are unclear. Some .env.example files exist but don't document which variables are required vs optional.

Context

Developers waste time debugging configuration issues that could be caught at setup time.

Proposed Solution

Update/create .env.example files for API and Oracle with:

• Comments explaining each variable
• Required vs optional marking
• Example values for testnet
• Links to where to get values (e.g., Stellar Laboratory for keys)

Acceptance Criteria

• api/.env.example with all variables documented
• oracle/.env.example with all variables documented
• Required vs optional clearly marked
• Example values are safe (testnet, not mainnet)

Technical Notes

• Files: api/.env.example, oracle/.env.example

Constraints

• Never include real secrets in examples

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 100 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave