And thanks so much for your involvement and interest 🙂
Yes, you can do that. But it's not a good method to resolve this problem, I have many applications, temporarily configuring nginx to intercept these requests is not elegant enough.
In addition, upgrade the webserver is also very complicated due to the new version file name change,
If I can config the prefix path of webserver, nginx routing will become very simple.
Thanks for your reply, I deploy clearml webserver in k8s successfully, and I can access it through http://<ip>:30080/  .
Now, I want access it through a nginx server, eg  http://<my-domain>/clearml  , after I configured nginx, I got a empty page.Â
I saw <script src="runtime-es2015.6afafe9b333cf9dcff7d.js" crossorigin="use-credentials" type="module">  in the html resource code, it will load http://<my-domain>/runtime-es2015.6afafe9b333cf9dcff7d.js  instead of http://<my-domain>/clearml/runtime-es2015.6afafe9b333cf9dcff7d.js  , so the browser cannot load the js file correctly.
Finally, I hope you can build the webserver like this <script src="./runtime-es2015.6afafe9b333cf9dcff7d.js" crossorigin="use-credentials" type="module"> , then the browser can load static file through relative path, or can you export a docker param to config prefix url path?
Hi JealousSealion33 . We are planning on releasing a clearml k8s package very soon. I hope this is something that you will be able to use. If not, could you please elaborate on the issue you are facing and share the error you are receiving?
If the request is for http://<my-domain>/runtime-es2015.6afafe9b333cf9dcff7d.js , you can setup nginx to intercept the request, modify the path and forward it as http://<my-domain>/clearml/runtime-es2015.6afafe9b333cf9dcff7d.js
JealousSealion33 , as far as I know, both no prefix and ./ are relative
Since all requests are routed internally with an nginx running inside the webserver docker container, we can provide the nginx config file we use and you can override it as required (for example, to strip the prefix you're adding, before serving resources and requests)
Hi JealousSealion33 ,
these are relative paths to the base of the site.
please try to change <base href="/"> in index.html to the path of your sub folder.
Looking forward to the update of the webserver source code on github! 😆
Unless you modify the html code, it will always load absolute url path, so it's not the problem of webserver's nginx config.
This should happen in the next few days 😄