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.
Dev environment: Add settings necessary for https and reverse proxy #10265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dev environment: Add settings necessary for https and reverse proxy #10265
Changes from all commits
caff0fb
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@humitos I forgot to add in the PR description that this depends on readthedocs/common#176
But yes, it would be nice if you can check that it works with your previous usage of
--ngrok
-- no reason that it shouldn't!So a full demo would be:
inv docker.up --no-django-debug --http-domain=<your-ngrok-domain> --https
Note that
--https
adds some new stuff that might have worked fine with yourngrok
proxy - I have been running with an extra Nginx proxy in front that might have interfered more.