From ff54b3a4713a2da63bee20c9ec00a799bb411b1e Mon Sep 17 00:00:00 2001
From: Wyzlle <101371689+wyzlle@users.noreply.github.com>
Date: Wed, 4 May 2022 00:09:59 +0530
Subject: [PATCH] set up hasura starter

---
 Dockerfile | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 Dockerfile

diff --git a/Dockerfile b/Dockerfile
new file mode 100644
index 0000000..6a6390d
--- /dev/null
+++ b/Dockerfile
@@ -0,0 +1,30 @@
+FROM hasura/graphql-engine:v1.3.3
+
+# Enable the console
+ENV HASURA_GRAPHQL_ENABLE_CONSOLE=true
+
+# Enable debugging mode. It should be disabled in production.
+ENV HASURA_GRAPHQL_DEV_MODE=true
+
+# Heroku hobby tier PG has few limitations including 20 max connections
+# https://devcenter.heroku.com/articles/heroku-postgres-plans#hobby-tier
+ENV HASURA_GRAPHQL_PG_CONNECTIONS=15
+
+# Change $DATABASE_URL to your heroku postgres URL if you're not using
+# the primary postgres instance in your app
+CMD graphql-engine \
+    --database-url $DATABASE_URL \
+    serve \
+    --server-port $PORT
+
+## Comment the command above and use the command below to
+## enable an access-key and an auth-hook
+## Recommended that you set the access-key as a environment variable in heroku
+#CMD graphql-engine \
+#    --database-url $DATABASE_URL \
+#    serve \
+#    --server-port $PORT \
+#    --access-key XXXXX \
+#    --auth-hook https://myapp.com/hasura-webhook 
+#
+# Console can be enable/disabled by the env var HASURA_GRAPHQL_ENABLE_CONSOLE