feat: self-hosted hasura for DataLayer graphql API #23
Conversation
docker-compose.yaml
Outdated
| HASURA_GRAPHQL_DEV_MODE: ${DATALAYER_HASURA_DEV_MODE:-true} | ||
| HASURA_GRAPHQL_ENABLED_LOG_TYPES: "startup, http-log, webhook-log, websocket-log, query-log" | ||
| HASURA_GRAPHQL_ENABLED_APIS: "graphql,metrics" | ||
| HASURA_GRAPHQL_ADMIN_INTERNAL_ERRORS: "true" |
There was a problem hiding this comment.
should we default this to false? would not want to expose prod info by accident
| DATALAYER_HASURA_UNAUTHORIZED_ROLE=public | ||
| DATALAYER_HASURA_CORS_DOMAIN=* | ||
| DATALAYER_HASURA_ENABLE_TELEMETRY=false | ||
| # HASURA_GRAPHQL_METADATA_DATABASE_EXTENSIONS_SCHEMA: "chain_data_schema_1" |
There was a problem hiding this comment.
some explanation of this might be useful--or do you think it would be clear?
There was a problem hiding this comment.
i'll add a link to Hasura docs explaining each variable
docker-compose.yaml
Outdated
| retries: 5 | ||
|
|
||
| api-hasura: | ||
| image: hasura/graphql-engine:latest |
There was a problem hiding this comment.
are you sure you don't want to pin a version to this?
docker-compose.yaml
Outdated
| timeout: 5s | ||
| retries: 5 | ||
|
|
||
| api-hasura: |
There was a problem hiding this comment.
lets pick more descriptive namings here
instead of api-hasura => datalayer-api
instead of graphql-engine => indexer-api
instead of envio-postgres => indexer-db
instead of datalayer-postgres => datalayer-db
lmk wdyt : )
There was a problem hiding this comment.
agree on making them more descriptive but i like the tech being on the name
datalayer-graphql-api
indexer-postgres-db
but we can go with your naming too, don't have any particular preference
🤖 Linear
Closes GIT-76 GIT-77
Description
Note: this Hasura is a different service from the one that gets exposed for Envio