Add support for existing SSL certificates #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I like this option for sure. Since you're dealing with paths, this needs to be reflected in a few areas. Most notably, in a validator function within I'm sure I'm missing more edge cases! |
|
This one can do it: https://github.com/patrickhener/goshs |
pantsmanuk
added a commit
to pantsmanuk/updog
that referenced
this pull request
Apr 5, 2022
As per sc0tfree#32, added logic to ensure that both --cert and --key arguments are supplied.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As requested in #28, custom SSL certificate functionality is trivial with the werkzeug.serving.run_simple function.
Tested by generating SSL certificates with the command:
openssl req -x509 -days 365 -newkey rsa:2048 -keyout test-ssl.key -out test-ssl.crt