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
The jupyter-panel-proxy is quite powerful. But the apps are loaded once when the panel server is started.
I.e. does not support use cases where users are updating their app code. I see use cases where
The user is the developer and updates the code her self.
The user is just updating the code via git pull.
The user is just working on a shared drive where the code is being updated by another user or system team. This could be the case on a Jupyter Hub I am the product owner for at work.
Potential solutions could be
Enable adding --auto flag when the server starts. The problem is that this is not quite robust, i.e. the server might get stuck.
Enable adding the --reload flag when the server starts. The problem is that this is not quite robust. i.e. the server might get stuck.
Enable the user to somehow manually force a restart of the server. The problem is that it needs to be restarted on the same port and base_url.
Maybe this does not have to be solved by jupyter-panel-proxy. Maybe this is as simple as restarting the jupyter (hub) server?? And telling users how to do this :-) But at least this is not a working solution for binder where every change is gone once you restart the jupyter binder server.
The text was updated successfully, but these errors were encountered:
The jupyter-panel-proxy is quite powerful. But the apps are loaded once when the panel server is started.
I.e. does not support use cases where users are updating their app code. I see use cases where
git pull
.Potential solutions could be
--auto
flag when the server starts. The problem is that this is not quite robust, i.e. the server might get stuck.--reload
flag when the server starts. The problem is that this is not quite robust. i.e. the server might get stuck.port
andbase_url
.Maybe this does not have to be solved by jupyter-panel-proxy. Maybe this is as simple as restarting the jupyter (hub) server?? And telling users how to do this :-) But at least this is not a working solution for binder where every change is gone once you restart the jupyter binder server.
The text was updated successfully, but these errors were encountered: