A long time not paying attention hasura graphql-engine, the latest release from information already can see graphql-engine beta
stage, and it is currently v1.0.0-beta.2
estimated from the available production is not far off (actually can be used)
Here are some big changes, and inquiries about the bug fix on the concrete can refer to the official documentation
- graphql api address positive, and it had previously been
/v1alpha1/graphql
nowv1/graphql
but also for the v1 version of the address be fixed - allow-list query can be defined graphql-engine operation (query, mutation), it is very convenient
- Manual event trigger, we can handle event hand, it is still very convenient, for some abnormal state, can artificially control
- console offline mode, we can carry out some operations console in the case of useless network, rather than initiating a network request (you can easily see graphql schema ...)
- Optimizes server startup time
Reference docker-compose run the file
version: '3.6'
services:
postgres:
image: postgres
environment:
- "POSTGRES_PASSWORD:dalong"
volumes:
- ./db_data:/var/lib/postgresql/data
graphql-engine:
image: hasura/graphql-engine:v1.0.0-beta.2
ports:
- "8080:8080"
depends_on:
- "postgres"
environment:
- "HASURA_GRAPHQL_DATABASE_URL=postgres://postgres:dalong@postgres:5432/postgres"
- "HASURA_GRAPHQL_ENABLE_CONSOLE=true"
allow-list trial
- Adding allow-list
- Several recommended usage from official
development example, only allow-list, ci / cd enable convenient testing, product environment is recommended
Explanation
hasura graphql-engine is more powerful
Reference material
https://docs.hasura.io/1.0/graphql/manual/deployment/allow-list.html