Repository navigation
chore(HaRP-frp): install FRP from releases - #101
Merged
Merged
Conversation
Signed-off-by: Oleksandr Piskun <oleksandr2088@icloud.com>
15 of 17 tasks
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.
The Dockerfile downloads frpc 0.61.1 from the
exapps_devfolder of the HaRP repository. HaRP will not add newer FRP archives there, and 0.61.1 is outside frp's compatibility guarantee for the frps 0.71.1 that HaRP now ships. The Dockerfile now installs frpc 0.71.1 from the official FRP release and checks the archive against the release'sfrp_sha256_checksums.txt, the same way app-skeleton-python and test-deploy do.Reference: nextcloud/HaRP#88