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
{{ message }}
This repository has been archived by the owner on Oct 6, 2023. It is now read-only.
For self-hosting, is it possible to proxy the zedrem daemon using nginx? If yes, would you be able to publish instructions on how to do it? Reason is to use virtual hosts to have multiple services running under port 443.
The text was updated successfully, but these errors were encountered:
For self-hosting, is it possible to proxy the zedrem daemon using nginx? If yes, would you be able to publish instructions on how to do it? Reason is to use virtual hosts to have multiple services running under port 443.
Reply to this email directly or view it on GitHub: #11
It is possible to proxy through nginx (which does support websockets). There would need to be some changes as to how zedrem establishes the connection though:
The server implementation in Zedrem should not require any changes and the Zed app itself should inherit these capabilities from the browser anyway (I haven't verified this yet).
This would be a great feature to have, I imagine it would be a pretty common use case for small organisations.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Dear Zedapp Team,
For self-hosting, is it possible to proxy the zedrem daemon using nginx? If yes, would you be able to publish instructions on how to do it? Reason is to use virtual hosts to have multiple services running under port 443.
The text was updated successfully, but these errors were encountered: