Skip to main content

​
Hasura add-on

​
Running Hasura

To provision a Hasura instance, add an empty deploy.addons.hasura section to the deployment manifest. Provide some basic configuration: 
deploy:
  env:
    HASURA_GRAPHQL_ADMIN_SECRET: "$\{\{ secrets.HASURA_SECRET \}\}"
    HASURA_GRAPHQL_UNAUTHORIZED_ROLE: user
    HASURA_GRAPHQL_STRINGIFY_NUMERIC_TYPES: "true"
  addons:
    postgres:
    hasura:
Note the use of a Cloud secret for storing the admin password.

​
Configuring a Hasura API

​
For a squid

Use the Hasura configuration tool for squids running dedicated Hasura instances. To make Cloud initialize Hasura configuration on squid restarts, make sure that the tool runs on squid startup by adding a deploy.init section to the manifest, e.g. like this: 
deploy:
  init:
    env:
      HASURA_GRAPHQL_ENDPOINT: 'http://hasura:8080'
    cmd:
      - npx
      - squid-hasura-configuration
      - apply
See also the Hasura section of the GraphQL guide and the complete squid example.

​
For a DipDup indexer

DipDup also configures Hasura automatically. See the DipDup section for details.