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
I'm running JupyterHub on Kubernetes based on the z2jh tutorial.
There is quite a bit of discussion online regarding options for deleting non-empty folders (e.g. here). My understanding is that currently deleting non-empty folders works in JupyterLab if you have send2trash installed, but since we don't have "trash" on JupyterHub this feature is disabled and the best option is rm -rf when necessary (reference here).
We've been using this approach for a while, but one of our less experienced users has just accidentally executed rm -rf /* in their terminal and deleted everything in their personal file space, plus most of the files on our shared drive! Luckily we have some snapshots for recovery, but I think an "Are you really sure?" warning message in the UI would actually be less dangerous than rm -rf, given that many JupyterHub users are not necessarily familiar with the Linux terminal.
I guess an ideal solution would be some kind of trash/recycle bin, but I guess this may be tricky to setup for JupyterHub on Kubernetes?
The text was updated successfully, but these errors were encountered:
I'm running JupyterHub on Kubernetes based on the z2jh tutorial.
There is quite a bit of discussion online regarding options for deleting non-empty folders (e.g. here). My understanding is that currently deleting non-empty folders works in JupyterLab if you have
send2trash
installed, but since we don't have "trash" on JupyterHub this feature is disabled and the best option isrm -rf
when necessary (reference here).We've been using this approach for a while, but one of our less experienced users has just accidentally executed
rm -rf /*
in their terminal and deleted everything in their personal file space, plus most of the files on ourshared
drive! Luckily we have somesnapshots
for recovery, but I think an "Are you really sure?" warning message in the UI would actually be less dangerous thanrm -rf
, given that many JupyterHub users are not necessarily familiar with the Linux terminal.I guess an ideal solution would be some kind of trash/recycle bin, but I guess this may be tricky to setup for JupyterHub on Kubernetes?
The text was updated successfully, but these errors were encountered: