GraphQL Hive について
Prevent breaking changes, monitor performance of your GraphQL API, and manage your API gateway.
Features
Schema Registry
GraphQL Hive offers 3 useful features to manage your GraphQL API:
- Prevent breaking changes - GraphQL Hive will run a set of checks and notify your team via Slack, GitHub, or within the application.
- Data-driven definition of a “breaking change” based on Operations Monitoring.
- History of changes - an access to the full history of changes, even on a complex composed schema (Federation, Stitching).
- High-availability and multi-zone CDN service based on Cloudflare to access Schema Registry
Monitoring
Once a Schema is deployed, it is important to be aware of how it is used and what is the experience of its final users.
Environment variables
View environment variables
- PROJECT
- hive
- DOMAIN
- stack.localhost
- DOCKER_REGISTRY
- "ghcr.io/graphql-hive/"
- DOCKER_TAG
- ":main"
- HIVE_ENCRYPTION_SECRET
- "11111111111111111111111111111111"
- HIVE_APP_BASE_URL
- "https://$PROJECT.$DOMAIN"
- HIVE_EMAIL_FROM
- "no-reply@graphql-hive.com"
- SUPERTOKENS_API_KEY
- "11111111111111111111111111111111"
- CLICKHOUSE_USER
- "clickhouse"
- CLICKHOUSE_PASSWORD
- "11111111111111111111111111111111"
- REDIS_PASSWORD
- "11111111111111111111111111111111"
- POSTGRES_USER
- "postgres"
- POSTGRES_PASSWORD
- "11111111111111111111111111111111"
- POSTGRES_DB
- "registry"
- MINIO_ROOT_USER
- "minioadmin"
- MINIO_ROOT_PASSWORD
- "minioadmin"
- CDN_AUTH_PRIVATE_KEY
- "11111111111111111111111111111111"