added workaround to avoid full upload #278
Open
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
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.
I would like to join the discussion at #119 but the conversation has been locked and limited to collaborators. So I'm creating a PR instead.
This workaround may race sub-domain name among other users but the effect should be limited since naming conflict will only happen when hash collision occurs.
I still prefer to store files on surge.sh over IPFS since I cannot guarantee my node is online when the resource is being requested.
The advantage of using surge.sh over Github and GitLab is that I can choose to list or unlist the item according to the need. GitLab page seems to support private repo but I've not figured out how to even start the GitLab page.