DOCS vx.y

New workflow vs the old workflow¶

This document is described in terms of new terminologies. In the following, even in the older workflow, new terms are used. Refer Terminologies and concepts.

Creating a Hasura project¶

Old workflow (<= v0.14.x)	New workflow (>= v0.15.x)
No specific workflow to create a project. Usually one heads to dashboard.platform.hasura.io and creates a cluster and then manually associates it to a project.	Use the `hasura` cli to create a project. Start with an pre-built project using `hasura clone`, or start a fresh project: `hasura clone base`. For more details refer: Hasura project.

Creating a Hasura cluster¶

Old workflow (<= v0.14.x)	New workflow (>= v0.15.x)
Go to dashboard.platform.hasura.io and create cluster from there. Admin credentials to the cluster are sent over email.	Install Hasura on any Kubernetes cluster or create a Pro tier cluster using the CLI. Add a cluster to an existing project by `hasura cluster add <cluster-name>`. For more details refer: Hasura cluster.

Opening the console¶

Old workflow (<= v0.14.x)	New workflow (>= v0.15.x)
Login to the cluster console (console.projectname42.hasura-app.io) using the admin credentials.	Open the console and connect it to any added cluster by running `hasura api-console`.

Creating tables¶

Old workflow (<= v0.14.x)	New workflow (>= v0.15.x)
Login to the cluster console, head to Data -> Schema page. Use Create Table page to create a table.	Open the API console by using `hasura api-console`. Head to Data -> Schema page. Use Create Table page to create a table. For more details refer Creating a table.

Configuring auth/notify/filestore¶

Old workflow (<= v0.14.x)	New workflow (>= v0.15.x)
Login to the cluster console, head to the specific microservice’s configuration page. Edit values from there and save.	Edit the appropriate files in `conf/{auth,notify,filestore}.yaml` to change Auth, Notify and Filestore settings. To apply these changes to a cluster, git commit and push to that cluster. `git commit && git push hasura master`. Refer Auth configuration, Hasura Notify (Sending emails/SMS), Hasura Filestore.

Adding a git-push microservice¶

Old workflow (<= v0.14.x)	New workflow (>= v0.15.x)
Login to the cluster console, head to Git Push Microservices page. Use Create page to create a git push microservice.	Use the hasura cli. Refer Adding custom microservices.

Adding a docker microservice¶

Old workflow (<= v0.14.x)	New workflow (>= v0.15.x)
Login to the cluster console, head to Git Push Microservices page. Use Create page to create a git push microservice.	Use the hasura cli. Refer Adding custom microservices.

API gateway settings¶

Old workflow (<= v0.14.x)	New workflow (>= v0.15.x)
Login to the cluster console, head to API Gateway page. Edit settings there and save.	Edit `conf/{domains,http-directives,routes}.yaml` to change any API Gateway settings, including routing to microservices. git commit and push to apply these changes to the cluster. For more details, refer Hasura API Gateway.

Managing SSH key¶

Old workflow (<= v0.14.x)	New workflow (>= v0.15.x)
Login to the cluster console, head to CLI > SSH Keys page. Add, view and remove keys from there and save.	Using hasura cli. `hasura ssh-key add/remove/list`. For more details, refer Hasura CLI: hasura platform:ssh-key.

Cluster access settings¶

Managing environment variables¶

Viewing logs/events¶

Old workflow (<= v0.14.x)	New workflow (>= v0.15.x)
Login to the cluster console, head to particular microservice’s page. Go to Logs page from there to view that microservice’s logs.	Using the hasura cli. `hasura microservice logs <microservice-name>`. For more details, refer Hasura CLI: hasura platform:microservice logs.

« previous | next »

Was this page helpful?