Fixes srs_setup.sh to use .env instead of hardcoded values #82
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
Programmierus
changed the title
|
For some reason I can't request review from team members :( List of Reviewers is empty |
|
@Programmierus the PR is still in draft, maybe that's why you can't request reviews? |
|
@boldkoala4615 I don't think it is:
|
|
Wonder why this is not being accepted... |
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.
The current srs_setup.sh script uses a hardcoded
../resourcesvalue that can indeed be altered in the.envfile's TODO section. This results in G-Points being downloaded to an incorrect location, subsequently causing them to be missing when starting with docker-compose. This pull request addresses and resolves this issue.