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
Shoko should support baseUrl or prefix settings, either through the web interface (and thus manually set within the application) or through the nginx header X-Script-Path (and thus configured at the server level instead, with Shoko operating as expected when the header is passed).
Use case: Placing Shoko behind a reverse proxy. Shoko right now can only be hosted on the root directory on a server instance, whether it be on a subdomain or main domain. This is because Shoko has no way to rewrite the urls when placed behind a reverse proxy.
Adding support for this would enable reverse proxy use for shoko using a location directive, e.g.
This will likely not happen for a while as there is APIs exposed as part of Shoko Server’s support for Desktop that can be considered relatively insecure.
Shoko should support baseUrl or prefix settings, either through the web interface (and thus manually set within the application) or through the nginx header X-Script-Path (and thus configured at the server level instead, with Shoko operating as expected when the header is passed).
Use case: Placing Shoko behind a reverse proxy. Shoko right now can only be hosted on the root directory on a server instance, whether it be on a subdomain or main domain. This is because Shoko has no way to rewrite the urls when placed behind a reverse proxy.
Adding support for this would enable reverse proxy use for shoko using a
location
directive, e.g.The text was updated successfully, but these errors were encountered: