Team Kode
ย ยทย AI-powered software agency

Managing Development and Production Environments in FlutterFlow and Supabase

Project Settings

Hello everyone! I'm setting up a project using FlutterFlow and Supabase and have some questions about managing different environments for development and production. I would appreciate any insights or experiences you can share!

  1. FlutterFlow URLs for Testing and Production: How can I manage to have separate URLs in FlutterFlow for testing and production environments? I need to send a test URL to my client for approval before going live.

  2. Supabase Configuration for Development: What specific configurations should I follow in Supabase to ensure that my development environment only interacts with my dev database and not production?

  3. Integrating New Features: Once features are tested in the dev environment, what's the best practice for integrating these into the production environment in both FlutterFlow and Supabase?

Looking forward to your tips on streamlining this process. Thank you!

What have you tried so far?

So far, I've looked into setting up separate environments for development and production using branching features in both FlutterFlow and Supabase. I've enabled branching in Supabase to create a separate test instance and explored how to manage different URLs in FlutterFlow for testing and live deployments. However, I'm seeking advice on the best practices for configuration settings in Supabase to ensure the development environment only interacts with the dev database and efficient methods for integrating tested features into production.

Did you check FlutterFlow's Documentation for this topic?
Yes
4
1 reply