Merge pull request #341 from aura-nw/feat/create-hasura-metadata-merg…

…e-develop

feat: manage hasura metadata (develop)

.env.hasura.sample

@@ -0,0 +1,4 @@
+# Use for hasura cli
+HASURA_GRAPHQL_VERSION=3
+HASURA_GRAPHQL_ENDPOINT=
+HASURA_GRAPHQL_ADMIN_SECRET=

.gitignore

@@ -59,6 +59,7 @@ typings/
 
 # dotenv environment variables file
 .env
+.env.hasura
 
 # next.js build output
 .next

Dockerfile

@@ -1,5 +1,8 @@
 FROM node:16-alpine
 
+## Install hasura cli
+RUN apk update && apk add bash curl && curl -L https://github.com/hasura/graphql-engine/raw/stable/cli/get.sh | bash
+
 # Working directory
 WORKDIR /app
 

README.md

@@ -56,12 +56,36 @@ then start service
 
 ```
 # create file env
-cp .env.example .env
+cp .env.sample .env
 
 # run with moleculer cli
 npm run dev
 ```
 
+### Hasura metadata migration
+
+Read [link](https://hasura.io/docs/latest/hasura-cli/install-hasura-cli/) to install Hasura CLI for your operating system. To make update to hasura metadata programmatically, use sample code below:
+
+```
+# init hasura directory
+hasura init hasura
+
+# create file env hasura
+cp .env.hasura.sample hasura/.env
+
+# go to hasura directory
+cd hasura
+
+# export current metadata from hasura
+hasura metadata export
+
+# check current diff between local and hasura server
+hasura metadata diff
+
+# apply current hasura metadata to server
+hasura metadata apply
+```
+
 ## Configuration
 
 [Config Moleculer](.env.sample), refer [docs](https://moleculer.services/docs/0.14/configuration.html) to get detail configurations