3 ms·

Everything in Hasura is configured declaratively. The web GUI is essentially just updating that configuration. There are a few options: 1. You use the GUI and

Everything in Hasura is configured declaratively. The web GUI is essentially just updating that configuration. There are a few options: 1. You use the GUI and then export/import the metadata 2. You can use the GUI and as you do, the GUI will keep incrementally updating the metadata configuration file and even create database migrations for you in your folder on your machine, kind of like an IDE 3. You can stop using the UI altogether, and just write the configuration by hand Docs: https://hasura.io/docs/1.0/graphql/manual/migrations/index.html https://hasura.io/docs/1.0/graphql/manual/migrations/index.h... Also, feel free to ask around on our discord if you need help: https://discord.gg/hasura https://discord.gg/hasura

adav 6y ago
This approach means one’s own deployments of Hasura can’t be immutable?
- tango12 6y ago
  There's a docker image that can take a configuration file as input. https://hasura.io/docs/1.0/graphql/manual/migrations/advanced/auto-apply-migrations.html https://hasura.io/docs/1.0/graphql/manual/migrations/advance... You can choose to bring in that configuration via a Kubernetes configmaps type thing, or by baking a new image for a release (like you would have done with your source code say).
  - adav 6y ago
    Yep, that’s what I’ve been doing for my experiments with Hasura so far :) It just feels a little “off-piste”.