Hello guys! In this video the biggest part is preparation and explanation of the use-case where seed migrations could be useful. So If you would like to jump right to the seed migration implementation - use time codes in video description (or click this: 00:12:14 ). Also pay your attention on creation Hasura's seed migrations with Hasura CLI hasura.io/docs/1.0/graphql/core/hasura-cli/hasura_seeds_create.html It is another way to create it but so far this kind of seed migrations are not "smart" enough comparing to what we implement in the video. You can not roll back them and can not use auto-apply with seeds created by CLI. Once Hasura CLI seeds get more features I will create a separate video.
Thanks Dmytro, how about save test data by Hasura seeds and populate it in run time for automation tests? Can I generate test data by application and after Hasura will detect new data and based on new data create seeds? is it possible?
Hi, can you please help me with this issue: Current Setup: 1) Using Digitial Ocean one click setup 2) Followed the steps to replace the HASURA_GRAPHQL_DATABASE_URL with my RDS postgres url which is on this pattern: postgres://
Hi, I can't know what kind of problem you could have. it could be that you forgot to restart your Hasura container after changing the HASURA_GRAPHQL_DATABASE_URL variable. If it is not a case you had better to ask on StackOverflow or in Hasura's GitHub.
Hi, thanks for your question! It is another place where you can store your migrations. So far it has no so much advantages to store them there because now it has some limitations like: it can not be auto-applied and can't be rolled-back but in the future I am sure it will be fixed and then it will be appropriate way but for now you'd better use the way described in the video.
![Hasura migrations [GraphQL engine, pragmatic overview, 2020]](http://i.ytimg.com/vi/edeJZz022AY/mqdefault.jpg)
🎉 The complete course about Hasura with Angular, React & Firebase Cloud Functions is available bit.ly/complete-hasura-course! 🎉
Hello guys! In this video the biggest part is preparation and explanation of the use-case where seed migrations could be useful. So If you would like to jump right to the seed migration implementation - use time codes in video description (or click this: 00:12:14 ). Also pay your attention on creation Hasura's seed migrations with Hasura CLI hasura.io/docs/1.0/graphql/core/hasura-cli/hasura_seeds_create.html
It is another way to create it but so far this kind of seed migrations are not "smart" enough comparing to what we implement in the video. You can not roll back them and can not use auto-apply with seeds created by CLI. Once Hasura CLI seeds get more features I will create a separate video.
Thanks Dmytro, how about save test data by Hasura seeds and populate it in run time for automation tests? Can I generate test data by application and after Hasura will detect new data and based on new data create seeds? is it possible?
Hi, can you please help me with this issue:
Current Setup:
1) Using Digitial Ocean one click setup
2) Followed the steps to replace the HASURA_GRAPHQL_DATABASE_URL with my RDS postgres url which is on this pattern: postgres://
Hi, I can't know what kind of problem you could have. it could be that you forgot to restart your Hasura container after changing the HASURA_GRAPHQL_DATABASE_URL variable. If it is not a case you had better to ask on StackOverflow or in Hasura's GitHub.
@@DecodedFrontend Yeah; created an issue on github. I restarted the container; checked again same problem.
Do you have any tutorial on accessing the external PG instance with Hasura and then using it?
Unfortunately I have no tutorials about it but I tried couple of month ago to connect Hasura to remote DB and it worked fine.
What is "seeds" directory for?
Hi, thanks for your question! It is another place where you can store your migrations. So far it has no so much advantages to store them there because now it has some limitations like: it can not be auto-applied and can't be rolled-back but in the future I am sure it will be fixed and then it will be appropriate way but for now you'd better use the way described in the video.