Repository navigation
[Docker] Suggestion: support base path for selfhosting #352
Description
Activity
please test
-e TP_URLBASEon thedeveloptagThanks, great work! Seems to be okay. However it is not yet implemented in docker mods for me and putting
xxx.xxx.xxx.xxx/themeparkurl inTP_DOMAINenv variable resulted in sed errors.use
TP_DOMAIN=domain.com\/themeparkReacted by Samuel BartíkGreat, it works! Thanks!
I have just noticed that when accessing the base theme css files via web, they have an @import statements with url that has
httpscheme despite havingTP_SCHEME=httpsenv variable set up. When Icatthe css file, those same urls hadhttpsscheme, but they were missing the base path.So: when acessing
- Via web:
@import url("http://xxx.xxx.xxx.xxx/themepark/css/base/bazarr/bazarr-base.css?sha=None"); - Directly the css file located in
/config/www/cssfolder:@import url("https://xxx.xxx.xxx.xxx/css/base/bazarr/bazarr-base.css?sha=None");
- Via web:
make sure you reverse proxy the https port or access locally using the https port
Yup, I was connecting to theme-park via http from the reverse proxy point of view. Nonetheless, it seems kind of strange. I would think that the scheme depended entirely on what I set in the env variable. Is this the intended behaviour?
- locked and limited conversation to collaborators
on Mar 30, 2022
Hello, I think it would be really handy to support base path so that the css can be accessed behind reverse proxy with url:
xxx.xxx.xxx.xxx/themepark.