local vs deployed - issue with base URL

[elx42]

Hi,
Thank you very much for this wonderful project.

I was playing around with mesop in the last days and locally everything I did worked flawlessly. Now, I wanted to deploy my application on our clusters and do face an issue with paths.
On my local machine, I can access the application via

http://localhost:9000/<page_path>

On our cluster, the deployment is accessible via
https://<CLUSTERNAME>/webapps/mesop/testing/<page_path>

In the latter case, I can see 404 issues in the console, as files can not be accessed on https://<CLUSTERNAME>/.

We tried to hack this by applying a fix in our Dockerfile
RUN sed -i 's|<base href="/".*/>|<base href="/webapps/mesop/testing/" />|' /opt/conda/lib/python3.11/site-packages/mesop/web/src/app/prod/web_package/index.html

Which solved some of the issues, but other requests also refer to the base URL and subsequently fail.

Does mesop support environment-specific configuration files that I could provide to set the base URL dynamically based on the environment the application is running? Or is there a different way I could solve this issue?

Many thanks!

[wwwillchen]

This isn't something that we support right now, but would be good to support - I'll mark this as a feature request

[elx42]

Thank you for the feedback, and considering this as a feature!

We were trying to play around with the gunicorn SCRIPT_NAME variable, but this was also not successful as it then led to issues in other parts of the deployment. We'll hold this one for the moment, but I will update this issue here, in case we do find something in the meantime before this feature is added.

[jWinman91]

Has there been an update on this issue since I ran in a similar issue? Or does anybody know a workaround?

[jWinman91]

I found a workaround by modifying the Dockerfile (using Python 3.11 on a ubuntu machine), inspired by your idea @elx42. Here are the Dockerfile modifications:

RUN sed -i 's|href="./styles.css".*/>|href="./PAGE_PATH/styles.css" />|' /usr/local/lib/python3.11/site-packages/mesop/web/src/app/prod/web_package/index.html
RUN sed -i 's|href="./favicon.ico".*/>|href="./PAGE_PATH/favicon.ico" />|' /usr/local/lib/python3.11/site-packages/mesop/web/src/app/prod/web_package/index.html
RUN sed -i 's|src="zone.js/bundles/zone.umd.js">|src="./PAGE_PATH/zone.js/bundles/zone.umd.js">|' /usr/local/lib/python3.11/site-packages/mesop/web/src/app/prod/web_package/index.html
RUN sed -i 's|src="prod_bundle.js"|src="./PAGE_PATH/prod_bundle.js"|' /usr/local/lib/python3.11/site-packages/mesop/web/src/app/prod/web_package/index.html
RUN sed -i 's|/__ui__|/PAGE_PATH/__ui__|' /usr/local/lib/python3.11/site-packages/mesop/web/src/app/prod/web_package/prod_bundle.js

RUN mkdir /usr/local/lib/python3.11/site-packages/mesop/web/src/app/prod/PAGE_PATH
RUN cp -r /usr/local/lib/python3.11/site-packages/mesop/web/src/app/prod/web_package/* /usr/local/lib/python3.11/site-packages/mesop/web/src/app/prod/PAGE_PATH
RUN mv /usr/local/lib/python3.11/site-packages/mesop/web/src/app/prod/PAGE_PATH /usr/local/lib/python3.11/site-packages/mesop/web/src/app/prod/web_package/PAGE_PATH

The first lines change the path inside the index.html file from the mesop installation. The path to this file might differ for different installations. For some reason I also had to create a directory of that name. That's what's happening in the bottom lines.

Additionally, I had to integrate mesop into a FastAPI server, as described here. I set the path of the page as well as the route where mesop was mounted to to PATH_PAGE.

While this workaround resolves the issue for me, I believe the relative path handling in mesop needs improvement! This should likely be addressed in the library itself to avoid these manual modifications.