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

"What does the installer do?" is not an obvious place to find uninstall instructions #576

Open
nbastin opened this issue May 19, 2020 · 3 comments
Labels
needs-documentation Issue that can be solved with documentation

Comments

@nbastin
Copy link

nbastin commented May 19, 2020

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).

@manics
Copy link
Member

manics commented May 19, 2020

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).

@nbastin
Copy link
Author

nbastin commented May 20, 2020

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.

@nguyenvulong
Copy link

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.

@consideRatio consideRatio added the needs-documentation Issue that can be solved with documentation label Oct 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-documentation Issue that can be solved with documentation
Projects
None yet
Development

No branches or pull requests

4 participants