Closed
Conversation
…very well with the 5 seconds updates
Member
Author
|
This PR is becoming obsolete with #866. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When building a docker image for Hashtopolis, there will be an issue when the image later is updated and the container restarted. In such a case Hashtopolis is not able to figure out, that it was updated, as the build information remains set to
repository.In order to allow building docker containers which can later be updated and Hashtopolis being able to apply upgrades, it must include the git commit hash somewhere. This can be achieved by running
./build.shwhich will place the hash into a file which is then included in the docker build process.