> For the complete documentation index, see [llms.txt](https://atd-dts.gitbook.io/moped-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atd-dts.gitbook.io/moped-documentation/dev-guides/how-tos/launching-the-hasura-console.md).

# 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 through the CLI or staging and production Hasura consoles. The staging and production consoles are disabled in our deployments so manual updates are not possible. All schema updates to staging and production are applied through team-reviewed PRs that are merged and then applied by our** [**GitHub Action workflow**](https://github.com/cityofaustin/atd-moped/actions/workflows/migrations-metadata-deployment.yml)**.**&#x20;

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 data structure as is available to staging.&#x20;

You may need to create seed data specifically for local development, and you are encouraged to do so if a schema change affects seed data written for the previous schema. You can test starting up the cluster with seed data by using the guide [here](https://github.com/cityofaustin/atd-moped/tree/main/moped-database#getting-started).

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

You can't! they are disabled in our deployment configuration. 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 or production. All the work is done by the GitHub Action workflow mentioned above.
