Make bootstrap.py work better with intercepting proxies

Issue #11 Addresses the need to document getting the environment to be used by sudo -E. I managed to install TLJH successfully this morning on an ubuntu 18.04 instance running in an OpenStack private cloud. Things that I encountered that required it.

• http(s)_proxy settings to get through our firewalls
• SSL error from requests installing Miniconda3
• SSL error from npm

I believe that these can all be addressed by updating Installing on your own server

Before the sudo apt-get install python3 git curl

export http_proxy=<your_proxy>
export https_proxy=<your_proxy>
export REQUESTS_CA_BUNDLE=/etc/ssl/certs/ca-certificates
sudo npm config set strict-ssl false

and then insert " -E " in the pipe to python3:

curl https://raw.githubusercontent.com/jupyterhub/the-littlest-jupyterhub/master/bootstrap/bootstrap.py | sudo -E python3 - --admin <admin-user-name>

[fm75]

Add to troubleshooting - what happens if you misconfigure HTTPS.

• If key/certs are misconfigured Traefik won’t start on reload
• Its failure to restart is not obvious
• HTTP access continues to work
• add journalctl command that can be used to investigate, perhaps with example output.

[yuvipanda]

Apologies for the (very) late response. I think we can move this into two separate actionable issues:

1. Document that Let’s Encrypt won’t work in a private network
2. Have bootstrap.py print better error messages when it can’t reach the public internet.

I’ve opened a new issue (#330) for (1) and updated (#16) to account for 2. I’m going to close this now, but feel free to re-open / open new issues.

Again, I apologize for letting this be unanswered for so long, @fm75