Add -e/--env flag to specify environment files #207
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements a CLI flag to specify environment files, matching Honcho's behavior. This allows users to specify custom env files via command-line flag instead of only through the OVERMIND_ENV environment variable.
Changes:
The flag accepts comma-separated file paths and loads them after the default env files (~/.overmind.env, ./.overmind.env, ./.env), allowing flag-specified files to override default values.
Usage:
overmind start -e .env.local
overmind start -e .env.local,.env.development
overmind start --env .env.local,.env.development
Closes #206