I’m experimenting with Hasura for an MVP. Like you I wanted to have the schema config in code and version controlled. The docs are very lacking for this use cas

I’m experimenting with Hasura for an MVP. Like you I wanted to have the schema config in code and version controlled. The docs are very lacking for this use case. However I think I’ve worked out a decent compromise: - I start configuring the basics of my Hasura setup through the Admin GUI. - I then use the CLI to download the metadata with the command `hasura metadata export`. - Commit that to my repo. - Using the existing metadata files as a template, make any changes when required. - Use the cli-migrations docker image to apply my metadata on each deployment of Hasura (as detailed here: https://hasura.io/docs/1.0/graphql/manual/migrations/advanced/auto-apply-migrations.html https://hasura.io/docs/1.0/graphql/manual/migrations/advance...) Not sure if that’s the most efficient way to do it but it seems to work and it was pretty quick to setup.