4
Feature Request: Support for config.toml.local (gitignored local configuration overrides)
Source: supabase/supabase#39585 · opened by @jacekpl
Problem Statement When working in team environments or managing multiple local Supabase projects simultaneously, developers need to customize port configurations without creating git conflicts or requiring manual config file management. Current Challenges 1. Team Collaboration: • Multiple developers need different port configurations locally (e.g., one developer uses default ports 54321-54324, another uses 55321-55324 to avoid conflicts with other projects) • config.toml is committed to git, so local port changes either: - Create unwanted git diffs that shouldn't be committed - Require developers to manually stash/revert changes before committing - Risk accidentally committing local-only configurations 2. Multiple Local Projects: • Developers often work on multiple Supabase projects that need to run simultaneously (e.g., main project + microservice + testing instance) • Each instance requires unique ports to avoid conflicts…
No pledges yet. Be the first to back this.
Comments
Similar requests
Enhance GitHub Integration for Supabase to Support Full config.toml Configuration
2 votes · 0 comments
Infrastructure as Code / config.toml for production
14 votes · 0 comments
Allow Customization of /migrations Directory in config.toml for Supabase Migrations and Shadow Database
7 votes · 0 comments
Add `supabase config pull` command
62 votes · 0 comments
Webhooks which call Edge functions should be configured via config.toml
1 vote · 0 comments
No comments yet.