Hosting Augur Turbo's simplified package on Crust network #1222
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.
Hey there!
These changes in the cd-release workflow enables pinning the simplified package build folder to IPFS and Crust network.
It adds 2 new steps to the build job:
Pin to IPFSandPin to Crust.Pin to IPFSuploads the files in the build folder (./packages/simplified/build) to Crust's IPFS gateway and generates the corresponding CID as a variable namedhash.Pin to Crusttakes that CID and places storage order on Crust network.For this to work you need to set
CRUST_SEEDSsecret so please consider that before merging.An alternative to using Crust's gateway for IPFS pinning is using the
aquiladev/[email protected]github action which supports various IPFS pinning services like Pinata.This submission is for this bounty on gitcoin.