Fixed issue with .env.vagrant not setting RAILS_ENV variable #15709
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
|
You can't put RAILS_ENV into an .env file since RAILS_ENV defines which .env file will be read. There's got to be another place to put that in the Vagrant config. |
|
Ok, made the changes in the Vagrantfile instead. |
Gargron
approved these changes
Feb 11, 2021
chrisguida
pushed a commit
to Start9Labs/mastodon
that referenced
this pull request
Feb 26, 2022
…n#15709) * Fixed issue with .env.vagrant not setting RAILS_ENV variable * made change to fix RAILS_ENV issue in Vagrantfile instead of .env.vagrant
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.
When setting up a dev environment with Vagrant came across an issue. Because the RAILS_ENV variable wasn't set in .env.vagrant the dev database wasn't being set up.