-
Notifications
You must be signed in to change notification settings - Fork 21
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
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
Support HTTPS #36
Comments
I can see that it would be nice to have in the binary, but I would say it would be easier to use caddy as reverse proxy to denokv and if you are selfhosting you probably already are using nginx or caddy as the user facing server so it should be easy to setup with no extra problem |
That would be fine, but would suggest that example instructions be updated to make that ability to support that in a container easier. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As far as I can tell,
denokv
only supports HTTP connections and not HTTPS which limits its ability from a self hosting perspective from a security aspect.The text was updated successfully, but these errors were encountered: