Graphql-engine: docs: guide on using rails migrations with hasura

Created on 11 Dec 2018  路  13Comments  路  Source: hasura/graphql-engine

We need docs on using Rails migrations with Hasura.

This guide can go here: https://hasura.io/docs/1.0/graphql/core/guides/integrations/index.html.

docs migrations good first issue help wanted

Most helpful comment

Any update on this?

All 13 comments

Hey there!

I've been a Rails developer for a couple years now, and would love to contribute to this issue for Hacktoberfest, and learn more about Hasura in the process. Can someone please guide me regarding how I can proceed with tackling this issue?

@athityakumar Hasura has migrations and metadata. Simply speaking, migrations are sql files and metadata is configuration like track_table, permissions, remote_schemas etc (configuration for all hasura features).

So, if somebody is running a rails microservice they might be using active record migrations to do the sql migrations already. But for these migrations to work seamlessly with hasura, they will have to run the corresponding metadata API calls as well.

This issue is to give a simple technique which embeds the corresponding hasura metadata in the active record/rails migration system.

@tirumaraiselvan - Ah, got it. Is there any other similar already-documented guide/technique for other web frameworks (Django/MEAN) that I could use as reference for what is expected?

I think rails have to has hasura extension that makes automatic API calls to hasura.

I not prefer use rails migrations on a new project. But when I done migrations with hasura, rails dosn't now relationships. Also rails activestroage migrations is a problem. Also if use a gem that makes migration, it is not comfortable. If anybody want to work about this topics, I want to work too.

I can work on this issue if anyone suggest me an example about how to make metadata API calls to Hasura. Thank you.

@fastengineer Thanks for your help. But, we have already finished work on this and just need to put it out.

Is this out yet?

@rikinsk Can we pls publish this in the docs?

Waiting the docs.

@tirumaraiselvan Should I create a PR and reference this issue?

@ashishra0 Pls go for it.

Any update on this?

+1

Was this page helpful?
0 / 5 - 0 ratings