graphql-engine/install-manifests
Anon Ray a21f6cd648 introduce v1/graphql (fix #1368) (#2064)
Changes compared to `/v1alpha1/graphql`

* Changed all graphql responses in **/v1/graphql** endpoint to be 200. All graphql clients expect responses to be HTTP 200. Non-200 responses are considered transport layer errors. 

* Errors in http and websocket layer are now consistent and have similar structure.
2019-05-10 11:35:10 +05:30
..
azure-container update manifests to v1.0.0-alpha45 2019-05-06 16:58:57 +05:30
azure-container-with-pg update manifests to v1.0.0-alpha45 2019-05-06 16:58:57 +05:30
docker-compose introduce v1/graphql (fix #1368) (#2064) 2019-05-10 11:35:10 +05:30
docker-compose-https introduce v1/graphql (fix #1368) (#2064) 2019-05-10 11:35:10 +05:30
docker-compose-pgadmin introduce v1/graphql (fix #1368) (#2064) 2019-05-10 11:35:10 +05:30
docker-compose-postgis introduce v1/graphql (fix #1368) (#2064) 2019-05-10 11:35:10 +05:30
docker-run update manifests to v1.0.0-alpha45 2019-05-06 16:58:57 +05:30
google-cloud-k8s-sql update manifests to v1.0.0-alpha45 2019-05-06 16:58:57 +05:30
kubernetes update manifests to v1.0.0-alpha45 2019-05-06 16:58:57 +05:30
README.md add docker-compose-pgadmin manifest (close #1424) (#1494) 2019-02-07 17:20:27 +05:30

Hasura GraphQL Engine Installation Manifests

Various installation / deployment methods for Hasura GraphQL Engine

  1. Docker Compose
  2. Docker Compose with HTTPS using Caddy
  3. Docker Compose with PostGIS enabled Postgres
  4. Docker Compose with pgAdmin
  5. Docker run
  6. Kubernetes
  7. Azure Container Instance without Postgres
  8. Azure Container Instances with Postgres

License

All content in this directory is under MIT License.