feat: Docker using --noTLS #16
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
ineiti
approved these changes
Oct 3, 2023
|
found two issues |
…on by reverse proxy)
PascalinDe
force-pushed
the
noTLS-docker
branch
from
125797a
to
bd03808
Compare
|
also now includes a script similar to run_local to run helper functions w/ Docker environment as well as some cleanup |
PascalinDe
force-pushed
the
noTLS-docker
branch
from
bd03808
to
4d69872
Compare
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.
adapt Dockerfile and docker-compose.yml to integrate changes necessary for
--noTLS