diff --git a/docs/testing-deployment-publishing/development-environments/development-environments.md b/docs/testing-deployment-publishing/development-environments/development-environments.md index a17a05fc..09ae1a5e 100644 --- a/docs/testing-deployment-publishing/development-environments/development-environments.md +++ b/docs/testing-deployment-publishing/development-environments/development-environments.md @@ -54,7 +54,7 @@ You can create and switch environments in the **Dev Environments** page in **App

-The selected environment is used to generate the proper app code when you run, test, deploy or export your app. The only things that change between environment are the [Firebase Project](#configuring-firebase-for-each-environment) or variables that are tied to [Environment Values](#use-environment-values) +The selected environment is used to generate the proper app code when you run, test, deploy or export your app. The only things that change between environment are the [Firebase Project](#configuring-firebase-or-supabase-for-each-environment) or variables that are tied to [Environment Values](#use-environment-values) ### Use Environment Values @@ -100,19 +100,63 @@ After switching to an environment, FlutterFlow generates code specific to that e You also may see different project errors depending on which environment you have selected. ::: -### Configuring Firebase for each Environment -A single FlutterFlow project can have **multiple environments**, each mapped to its **own Firebase project**. This ensures that environments like `Development`, `Staging`, and `Production` remain independent, giving you better control over your app's data and behavior throughout different stages of development. +### Configuring Firebase or Supabase for each Environment +A single FlutterFlow project can have **multiple environments**, each mapped to its **own Firebase or Supabase project**. This ensures that environments like `Development`, `Staging`, and `Production` remain independent, giving you better control over your app's data and behavior throughout different stages of development. -![flutterflow-environment](../imgs/flutterflow-environment.avif) +![flutterflow-environment](../imgs/flutterflow-environment-update.avif) -If your project uses Firebase, you'll need to [**manually configure a new Firebase project**](../../ff-integrations/firebase/connect-to-firebase-setup.md#connect-an-existing-firebase-project-manually) for each environment. This requires setting up a new project in the Firebase console and linking it to the selected environment in FlutterFlow. +You must complete the Firebase or Supabase setup for an environment before you can test your app using that environment. However, this doesn't stop you from continuing to run and test your app in other environments. Just switch back to Production, and you can keep testing while finishing the setup for the new environment. + +#### Configuring Firebase +If your project uses Firebase, you'll need to create a separate Firebase project in the Firebase Console for each environment. Then, you can change the selected environment in the Firebase settings page (see below), and follow the steps to [**manually configure the Firebase project**](../../ff-integrations/firebase/connect-to-firebase-setup.md#connect-an-existing-firebase-project-manually) for each one. + + +![firebase-dev-env-config.png](../imgs/firebase-dev-env-config.png) + +Additionally, you must manually set up [**Firestore rules**](../../ff-integrations/database/cloud-firestore/firestore-rules.md) and [**collections**](../../ff-integrations/database/cloud-firestore/creating-collections.md) for the new environment. :::info -- You must complete the Firebase setup for the new environment before you can test your app using that environment. However, this doesn't stop you from continuing to run and test your app in other environments. Just switch back to production, and you can keep testing while finishing the setup for the new environment. -- You must manually set up [**Firestore rules**](../../ff-integrations/database/cloud-firestore/firestore-rules.md) and [**collections**](../../ff-integrations/database/cloud-firestore/creating-collections.md) for the new environment. -- Data that you add to Firebase through the Content Manager is specific to the Firebase project, and environment, that you have selected +The data that you add to Firebase through the Content Manager is specific to the Firebase project, and environment, that you have selected. ::: +#### Comnfiguring Supabase +If your project uses Supabase, you'll need to [**set up a new Supabase project**](../../ff-integrations/supabase/supabase-setup.md) for each environment. + +Create environment-specific values like `SupabaseAPIURL` and `SupabaseAnonKey`, and then configure the Supabase properties to point to these newly created values. Below is an example of how it would look like. + +
+ +
+

+ +:::note +It's recommended that you keep schemas consistent between the different Supabase environments. It's also recommended that you +**Get Schema** from the Production environment and build from there. + ::: + + + ### FAQ diff --git a/docs/testing-deployment-publishing/imgs/firebase-dev-env-config.png b/docs/testing-deployment-publishing/imgs/firebase-dev-env-config.png new file mode 100644 index 00000000..eb928e30 Binary files /dev/null and b/docs/testing-deployment-publishing/imgs/firebase-dev-env-config.png differ diff --git a/docs/testing-deployment-publishing/imgs/flutterflow-environment-update.avif b/docs/testing-deployment-publishing/imgs/flutterflow-environment-update.avif new file mode 100644 index 00000000..9e4fde0f Binary files /dev/null and b/docs/testing-deployment-publishing/imgs/flutterflow-environment-update.avif differ