What problem does it solve?
Running two or more Envio HyperIndex projects locally with pnpm dev fails because the CLI creates Docker resources with fixed global names, causing container-name conflicts and one project's migrations clobbering another's data in the shared Postgres.
Core Features & Use Cases
- Per-project isolation: Set unique
ENVIO_PG_SCHEMA and ENVIO_INDEXER_PORT values in each project's .env so multiple indexers share one local Postgres without collisions.
- Hasura metadata caveat: Explains the last-writer-wins behavior of shared Hasura table tracking and when it matters.
- Dedicated Hasura workaround: Provides Docker commands to run a second Hasura instance per project, including fixes for enum type search_path, custom root fields, and numeric serialization.
- Use Case: You are developing three indexers for different chains on one machine and need each syncing simultaneously with its own queryable GraphQL API on separate ports.
Quick Start
Ask the assistant to set up a second Envio indexer project to run locally alongside an existing one without port or database conflicts.