-
-
Notifications
You must be signed in to change notification settings - Fork 764
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
feat: implement the possibility to add tls #4456
feat: implement the possibility to add tls #4456
Conversation
Signed-off-by: Wim de Groot <[email protected]>
feat: enable support for tls
@michael-genson, you seem to contribute a lot to this project. I'am not able to find anything about a process on asking for a review. Do you know how this works? |
Hey there! All of the maintainers contribute to Mealie in their spare time, so we don't really have a review schedule. We will get to it eventually, promise! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks for this! Could you add the new variables to the docs?
docs/docs/documentation/getting-started/installation/backend-config.md
.
You can put it between Webworker and LDAP (unless you think it's better somewhere else). And maybe add a small blurb that this is only for serving Mealie without a webserver/reverse proxy.
Signed-off-by: Wim de Groot <[email protected]>
What type of PR is this?
What this PR does / why we need it:
Mealie needs to have the option to use a TLS certificate, for the following cases:
Which issue(s) this PR fixes:
Fixes: #2294
Special notes for your reviewer:
I am not sure if the naming of the properties is in line with the project, I would like feedback on that.
Testing
I've tested this change by deploying the app to my homelab. Since the features of uvicorn are mostly used here I am not sure if there are more unit tests needed.