-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Custom Config File Support #3092
base: develop
Are you sure you want to change the base?
Conversation
Feature/custom config flag
Pull Request Test Coverage Report for Build 13083225214Details
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally agree to add this functionality. However, the current implementation doesn't handle changing workdir based on the given config path.
Adds support for setting the working directory based on the provided config file path: - Handles both absolute and relative config paths - Normalizes paths across platforms - Maintains Windows compatibility by handling drive letters - Preserves existing behavior when no config file is specified This addresses the feedback about workdir handling in the CLI by ensuring the working directory is properly set based on the config file location. Tests added: - Relative config paths - Absolute config paths - Non-existent config paths - Malformed config files
feat(cli): handle workdir based on config file path
Thanks for the feedback! I think I have addressed the issues with my latest changes. |
Add Custom Config File Support
Introduces a new
--config-file
flag to the Supabase CLI, enabling users to specify alternative configuration files. This enhancement allows running multiple parallel local development environments with different configurations (#2139).Example Usage
Benefits