hasura-docker-cli

Run Hasura CLI migrations in a self-hosted Docker deployment by executing commands via docker exec on your console container, targeting the graphql:8080 endpoint to apply or check migration status without cloud dependencies.

Yes, you can manage Hasura metadata and console access without a local CLI installation by running hasura-cli commands inside a Docker container to export, import, and reload metadata securely via docker exec.

To execute Hasura CLI commands inside a container, you need a Docker-compose configuration with a running console container, hasura-cli installed within it, and network access to the Hasura endpoints at graphql:8080 and console:9695.

Hasura CLI metadata export failing in a Docker container is often due to incorrect endpoint configurations; ensure your docker exec command correctly targets http://graphql:8080 and that the console container is running properly.

The best way to automate Hasura migrations and seeds in Docker is running hasura-cli migrate and seed commands inside your console container via docker exec, automating deployment tasks directly against your self-hosted endpoints.