How do I launch the Hasura Console?

Context

The Hasura console should only be run locally. You should already have all the data you need locally, and for the most part you will not need to look into production or staging environments. You will not be applying migrations directly against staging or production.

The production environment should be identical to staging, and your local environment should be branched off of staging (main branch), what this means is that you are running the same structure as is available to staging.

The data will be different, but if you need more data in those columns then maybe it is a seed data situation. You may need to create seed data specifically for local development, and you are encouraged to do so.

Video Tutorial

What if I still want to access the production or staging console?

You can, but you really shouldn't. Using the console opens the door for conflicts between all three environments, you should not be patching things in staging, no manual work or adjustments should ever be made via the console in staging, much less in production. All the work is done by CircleCI or GitHub actions.

What are your options?

• Use your favorite SQL client.

• Use Postman (in GraphQL mode) against Staging or Prod.

DANGER ZONE: To connect to the Hasura Console to staging or production, you need to create a file in the ./moped-database/config folder and name it hasura.staging.yaml or hasura.production.yaml (correspondingly), and provide all the details needed for hasura console to connect, including the endpoints and admin secrets:

version: 2
endpoint: <staging_endpoint_here>
metadata_directory: metadata
admin_secret: <staging_admin_secret_here>
actions:
  kind: synchronous
  handler_webhook_baseurl: <staging_endpoint_here_again>

---> ---> Please read the Hasura docs and find out why this is a terrible idea for you to do. --->

Postman and GraphQL: