Add documentation to set up Hawkbit in HTTPS from server start #10
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
This tutorial allows to set up the client and the Hawkbit server to use HTTPS from the start.
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.
What it is about
This PR adds documentation to help users to initially set up Hawkbit to work with HTTPS. It is linked to other PRs made into
dockerfiles/httpsandfullmetalupdate-cloud-demo.It also corrects the previous work done regarding HTTPS, with which you could not update your targets anymore.
Limitations
The process described here should only be used for test environments. Proper certificate generation may be done using
Let's EncryptandCertbotPython bot.