We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As of now, teddycloud and teddycloud_web assume that it runs directly on the root level at ip:port/
it would be nice if there was support for a path prefix (e.g. ip:port/teddycloud/), so it will be easier to run it behind a reverse proxy.
My workaround right now is filtering the javascript and html https://github.com/mrueg/addon-teddycloud/blob/main/teddycloud/rootfs/etc/nginx/servers/ingress.conf#L20 which is not ideal, as things change in teddycloud_web from time to time.
The text was updated successfully, but these errors were encountered:
have you tried to adapt the host url in the settings?
Sorry, something went wrong.
I have not, I'll give it a shot. Does the host url have an effect on the minimized js if there's a prefix?
i dont know, was just a thought
I tested it, at least I couldn't see any difference. :/
I'm not a frontend dev, but could we use https://vite-plugin-ssr.com/base-url and have it injected by teddycloud into the embedded JS during runtime?
No branches or pull requests
As of now, teddycloud and teddycloud_web assume that it runs directly on the root level at ip:port/
it would be nice if there was support for a path prefix (e.g. ip:port/teddycloud/), so it will be easier to run it behind a reverse proxy.
My workaround right now is filtering the javascript and html https://github.com/mrueg/addon-teddycloud/blob/main/teddycloud/rootfs/etc/nginx/servers/ingress.conf#L20 which is not ideal, as things change in teddycloud_web from time to time.
The text was updated successfully, but these errors were encountered: