dev: docker-compose: expose redis locally #887
Merged
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
Allowing access to enketo's redis instances locally allows this docker-compose environment to be used to work on enketo-express as well as other central services: 1. run in this repo: make stop && make dev && docker compose stop enketo 2. run in `enketo` repo: yarn workspace enketo-express grunt develop
sadiqkhoja
approved these changes
Feb 13, 2025
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.
Allowing access to enketo's redis instances locally allows this docker-compose environment to be used to work on enketo-express as well as other central services:
run in this repo:
make stop && make dev && docker compose stop enketo
run in
enketorepo:yarn workspace enketo-express grunt develop
What has been done to verify that this works as intended?
Tested locally.
Why is this the best possible solution? Were any other approaches considered?
No other approaches considered.
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
No effect.
Does this change require updates to documentation? If so, please file an issue here and include the link below.
No.
Before submitting this PR, please make sure you have:
nextbranch OR only changed documentation/infrastructure (masteris stable and used in production)