Hi @Luke_Singham,
That’s an interesting question. You already made the distinction between content served by the shinyproxy server and content served by the web server inside the docker container.
I think it’s important to maintain that distinction, and have any content for your custom app served by the server inside your container. The shinyproxy server should only serve content related to shinyproxy itself, e.g. the login page, the app overview page, etc.
These URLs get proxied to your container and will be served from there.
For shiny apps, this works because all content referenced from the shiny app’s page uses hrefs that are relative to the page, e.g.
<link href="shared/shiny.css" rel="stylesheet" />
This ends up going to
I’m afraid I am not familiar with Dash, but if your URL ends up as
Then that means the href being used was “/_dash-layout” and not “_dash-layout”.
Do you control the hrefs? If so, removing the slash may solve your issue. If not, it becomes trickier… you could use javascript and extract the correct URL from window.location.
Regards,
Frederick