Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support HTTPS #36

Open
kitsonk opened this issue Nov 20, 2023 · 2 comments
Open

Support HTTPS #36

kitsonk opened this issue Nov 20, 2023 · 2 comments

Comments

@kitsonk
Copy link

kitsonk commented Nov 20, 2023

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.
@EduM22
Copy link

EduM22 commented Dec 17, 2023

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

@kitsonk
Copy link
Author

kitsonk commented Dec 17, 2023

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
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kitsonk @EduM22