Description:
Deploy and maintain a public Fluid node on Testnet for the community to use during development.
Requirements and Context:
Requiring every developer to run their own Fluid node during development is a huge barrier to adoption. A shared Testnet node removes this friction.
Acceptance Criteria:
Deliverables:
NOTE: This issue will NOT be reviewed or approved without evidence (screenshot, log, or test output) demonstrating the feature works as described.
Suggested Execution:
- Deploy the Fluid stack to a cloud provider (Railway, Render, or AWS)
- Configure rate limits appropriate for the free tier
- Link from the developer portal and README
Guidelines:
- Follow the existing project coding conventions
- All new environment variables must be documented in
.env.example
- Phase: Phase 15: Community
Example Commit Message:
ops: deploy public community testnet fluid node
Description:
Deploy and maintain a public Fluid node on Testnet for the community to use during development.
Requirements and Context:
Requiring every developer to run their own Fluid node during development is a huge barrier to adoption. A shared Testnet node removes this friction.
Acceptance Criteria:
Deliverables:
NOTE: This issue will NOT be reviewed or approved without evidence (screenshot, log, or test output) demonstrating the feature works as described.
Suggested Execution:
Guidelines:
.env.exampleExample Commit Message: