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
There is a bug since then with the paths : local version works, but server version only allows to access the index pages,
but not the app pages (or the favicon, etc ...). Using the last commit 48d9b34 on the server now.
yes I've seen it yesterday and the problem relates to the relative/absolute paths of js/css files. Without a recursive structure the assets path were all relative and in the same route/folder structure. Now, they have to access the same files which are usually at the index route /.
But on the server this absolute path index route maps to the URL https://jupyterhub.mat.tu-harburg.de/ while we would need the URL https://jupyterhub.mat.tu-harburg.de/blockops/.
I tried to fix it with absolute paths that get generated at runtime by Flask which might already fix the problem. So if you upload the latest updates, it might work.
The text was updated successfully, but these errors were encountered:
There is a bug since then with the paths : local version works, but server version only allows to access the index pages,
but not the app pages (or the favicon, etc ...). Using the last commit 48d9b34 on the server now.
Response from @MichelKrispin :
yes I've seen it yesterday and the problem relates to the relative/absolute paths of js/css files. Without a recursive structure the assets path were all relative and in the same route/folder structure. Now, they have to access the same files which are usually at the index route
/
.But on the server this absolute path index route maps to the URL https://jupyterhub.mat.tu-harburg.de/ while we would need the URL https://jupyterhub.mat.tu-harburg.de/blockops/.
I tried to fix it with absolute paths that get generated at runtime by Flask which might already fix the problem. So if you upload the latest updates, it might work.
The text was updated successfully, but these errors were encountered: