Skip to content
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

Cleanup HTTPS documentation #328

Merged
merged 3 commits into from May 28, 2019
Merged

Conversation

yuvipanda
Copy link
Collaborator

@yuvipanda yuvipanda commented May 18, 2019

  • Wrap some lines
  • Normalize reference anchors to conform to hierarchy
  • Mention that the certificates will be renewed
  • Strengthen suggestion to use Let's Encrypt
  • Note that Let's Encrypt doesn't work in internal
    networks not accessible from the internet
  • Note that you need a domain name before you can
    set up HTTPS
  • Add section on troubleshooting HTTPS
  • Add section on getting traefik logs, and remove section
    on configurable-http-proxy (which we no longer use)

Fixes #305
Fixes #217

  • Add / update documentation

- Wrap some lines
- Normalize reference anchors to conform to hierarchy
- Mention that the certificates will be renewed
- Strengthen suggestion to use Let's Encrypt

Fixes jupyterhub#305
Also note that Let's Encrypt doesn't work in private
networks.

Fixes jupyterhub#217
We no longer use CHP, so add section on getting logs from
traefik instead
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document renewal process for HTTPS certificates Make it clearer that you always need a domain name for HTTPS
1 participant