You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If your install goes pear-shaped (see #575), you have to clean up what has been done but it's not obvious how to figure this out. At the very least it would be nice if there was a doc page that was titled in a way that made it likely you would find it, although it would also be very nice if the installer recorded a journal of installed paths and record external actions where that isn't possible (the process is terribly opaque right now, I'm not sure I could really trust the resulting installation anyhow from an audit standpoint).
The text was updated successfully, but these errors were encountered:
Thanks for the feedback! I'm not sure how much you know about JupyterHub- TLJH is intended to be an all-in-one easy to install distribution of JupyterHub.
Can you describe your auditing requirements? It may be that you're better off installing JupyterHub manually (e.g. pip install ... and create a configuration file), or use other deployment methods developed by the community (e.g. Ansible roles).
We have what seemed like the basic requirements - <100 users, so I thought I'd give TLJH a try (we've previously installed JH manually, but our installations are pretty crufty at this point so I'm trying to bring us up to something more modern).
From an auditing standpoint it's problematic that I don't know what packages it installs or where it gets anything from. We can of course monitor it during the install and capture the filesystem diffs afterwards, but right now the documentation is very opaque as to what is going to happen and the installer is then very opaque about what actually happened. Minimally for security reasons we have to report packages and software installs so that upgrades/mitigation can be managed site-wide when vulnerabilities are discovered.
Avoid TLJH at all cost, this repo is inactive, a lot of questions remain unanswered.
Have a look at my comment here and you can build it from ground up to completely have control over it. I guess this is the one that you said it is "crufty" but from what I have so far this is the best. The tutorials have errors too but they fix them some time.
If your install goes pear-shaped (see #575), you have to clean up what has been done but it's not obvious how to figure this out. At the very least it would be nice if there was a doc page that was titled in a way that made it likely you would find it, although it would also be very nice if the installer recorded a journal of installed paths and record external actions where that isn't possible (the process is terribly opaque right now, I'm not sure I could really trust the resulting installation anyhow from an audit standpoint).
The text was updated successfully, but these errors were encountered: