Branch: master
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
46 lines (32 sloc) 1.6 KB


By default, when you run the GraphQL engine you can use the Hasura console served by the GraphQL engine to make changes to your schema. However, if you have different environments or are adding GraphQL to an existing application or database, you'll need migrations to make sure that your iteration and CI/CD process is smooth.

Using Hasura migrations

Hasura GraphQL engine comes with powerful Rails-inspired migration tooling to help you keep track of the changes you make to your schema. As you use the Hasura console, the Hasura CLI will spit out migration files for you that you can put in version control and even edit manually.

Setup guides

Follow the guide that best fits your scenario:


.. toctree::

   For new project <new-project>
   For existing project <existing-project>
   With a database with an existing migration system <database-with-migrations>
   Auto-apply migrations/metadata when server starts <auto-apply-migrations>