fix: copy frontend .env from example in setup script#68
Open
mfisher31 wants to merge 1 commit intomieweb:mainfrom
Open
fix: copy frontend .env from example in setup script#68mfisher31 wants to merge 1 commit intomieweb:mainfrom
.env from example in setup script#68mfisher31 wants to merge 1 commit intomieweb:mainfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
setup.sh was not setting up the frontend environment file, causing
docker compose buildto fail when .env was absent (the Dockerfile copies it into the image).Changes:
cdinto frontend and copy .example.env →.envif one doesn't already exist, consistent with how the pulsevault subproject env is handledSCRIPT_DIRas an absolute path at the top of the script so subsequentcdcalls work correctly whether the script is invoked viabash scripts/setup.shor setup.sh