Summary
The remote DB dumps that local clients bootstrap from should be deployable via a CI action, similar to how subgraph and contract deployments work. Currently this is a manual process tied to one person.
Requirements
- Support multiple database configurations with separate URLs
- Deployable via GitHub Actions workflow dispatch
- Configuration pulled from
networks.json or similar (matching the subgraph pattern)
- New configurations can be added alongside old ones (parallel deployment, then deprecate old)
- The deployed URL should be available after the action completes
Context
From the rename PR (#2526), the DB schema changed (orderbook_address → raindex_address, schema version 2→3). Rather than updating existing dumps in-place, the plan is to deploy new dumps alongside the old ones and deprecate the old ones.
This is also a general improvement to avoid having critical infrastructure deployment tied to a single person.
Reference
The subgraph deployment pattern (deploy-subgraph.yaml + networks.json) is a good model to follow.
🤖 Generated with Claude Code
Summary
The remote DB dumps that local clients bootstrap from should be deployable via a CI action, similar to how subgraph and contract deployments work. Currently this is a manual process tied to one person.
Requirements
networks.jsonor similar (matching the subgraph pattern)Context
From the rename PR (#2526), the DB schema changed (
orderbook_address→raindex_address, schema version 2→3). Rather than updating existing dumps in-place, the plan is to deploy new dumps alongside the old ones and deprecate the old ones.This is also a general improvement to avoid having critical infrastructure deployment tied to a single person.
Reference
The subgraph deployment pattern (
deploy-subgraph.yaml+networks.json) is a good model to follow.🤖 Generated with Claude Code