fix: allow HTTPS server to run without certificates #207
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.
Currently, if the certificates folder does not exist, the HTTPS server fails to start. With the current setup, if any of the two servers (HTTP or HTTPS) exits, it stops the other one.
This is causing issue where, if the user does not have local-dns installed, they won't have the certificates folder, and by consequence the HTTPS server will not start and kill the HTTP server.
These changes allow the HTTPS server to start without any certificate.
Related to SHIP-2057