Disable loading .env file when running foreman for development #388
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We're actually fixing this in Kamal 2, which will be out before Rails 8, so that it uses .kamal/secrets instead of .env. So I'm not sure this is actually necessary, and would prevent the use of .env for legitimately passing on envs to foreman. |
|
Okay. But I think that tailwindcss-rails, cssbundling-rails, jsbunding-rails and dartsass-rails should generate a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Same as in rails/cssbundling-rails#155 and rails/jsbundling-rails@0ff85a2
We should just not load the .env when running foreman locally for bundling etc.