From b2eed614fa6acdd5ff775fbac5db55d56cc3404f Mon Sep 17 00:00:00 2001 From: Rob Dominguez Date: Fri, 27 Oct 2023 03:52:06 -0500 Subject: [PATCH] docs: update cloud to local dev steps PR-URL: https://github.com/hasura/graphql-engine-mono/pull/10421 GitOrigin-RevId: 12927dc8d2fea746c4dac8ee275870f4e10fdb8f --- docs/docs/hasura-cloud/environments.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/docs/hasura-cloud/environments.mdx b/docs/docs/hasura-cloud/environments.mdx index 80978a6a65b..f5e535a9583 100644 --- a/docs/docs/hasura-cloud/environments.mdx +++ b/docs/docs/hasura-cloud/environments.mdx @@ -23,12 +23,16 @@ import ProductBadge from '@site/src/components/ProductBadge'; ## Introduction -This guide will show how to configure your Hasura Project for easy switching between development environments. +This guide is designed to teach you how to set up and modify Hasura in a local Docker environment, and then transfer +those changes to your Cloud project. ## Moving from Hasura Cloud to local development ### Step 1: Setup local development of Hasura with Docker +In this step, you'll establish a self-hosted version of Hasura. **Please note: if you intend to utilize Hasura EE for +local development, secure a license by filing a ticket with [Hasura support](https://hasura.io/help/).** + Follow the guide [here](/getting-started/docker-simple.mdx) to get up and running with Hasura GraphQL Engine and Postgres as Docker containers in your local system. You can skip the steps involving connecting a database, as you'll be applying Metadata from your cloud database in a later step. Make sure that the ENV variable name for database connection