Skip to content
This repository has been archived by the owner on Oct 28, 2023. It is now read-only.

NEST-Desktop behind a proxy #16

Open
kreuzert opened this issue Jun 11, 2020 · 2 comments
Open

NEST-Desktop behind a proxy #16

kreuzert opened this issue Jun 11, 2020 · 2 comments

Comments

@kreuzert
Copy link

kreuzert commented Jun 11, 2020

Hi everyone,

I would like to use NEST-Desktop behind a proxy, but the javascript functions are looking for the assets on the wrong path. Is there a way to tell NEST-Desktop where to look for the assets?

Context:
I created a Docker image based on jupyter/datascience. I added a server proxy extension for JupyterLab and installed nest-desktop in a conda environment. (Dockerfile is here)

However, I'm able to run nest-desktop start in my JupyterLab Terminal. But if I want to open it at the path https://<my_jupyterhub_server>/user/user_name/server_name/proxy/8000/ it is looking for the assets at https://<my_jupyterhub_server>/hub/assets/... , while instead it has to use the path above.

Is there any way to configure nest-desktop in that way? I assume that there are more usecases for this, for example running NEST-Desktop behind a nginx proxy at a specific path.

Thanks,
Tim

Log from Firefox Console:
Object { headers: {…}, status: 404, statusText: "Not Found", url: "https://jupyter-jsc.fz-juelich.de/hub/assets/config/app/groups.json" ...

JupyterLab Screenshot
NEST-Desktop Screenshot

@babsey
Copy link
Owner

babsey commented Jul 1, 2020

Sorry for late response. Your issue is a special one.
I only started NEST Desktop from bash but I assume
that it would be possible to start it from the Python interface.

I notice two things in your screenshots:

  1. You have to start NEST Server before starting NEST Desktop. Starting NEST Server from Python will cause some unidentified error that crash the flask server instance. I fixed this problem, when I use older Flask ( < v1.0).
  2. I registered that NEST Desktop is not able to load json from assets folder.
    Is it a kind of permission issue of Jupyter notebook?

I am forward hearing from you whether jupyter notebook is able to work with NEST Desktop and NEST Server.

@kreuzert
Copy link
Author

kreuzert commented Jul 1, 2020

I will continue my tests with the nest server in the next days. But I remember to started it, maybe not in the runs with the screenshots.

The second point is exactly the reason, why I opened this issue. NEST Desktop is looking at the wrong place for the assets folder. I want NEST Desktop to look here: "https://jupyter-jsc.fz-juelich.de/user/[email protected]/my_jupyterlab_name/proxy/8050/assets" instead of "https://jupyter-jsc.fz-juelich.de/hub/assets". Is there a way to change the prefix path for the assets folder?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants