-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automate upload car for releases #39
Conversation
); | ||
} | ||
|
||
if (network !== "mainnet" && network !== "testnet") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is no NEARFS on testnet as far as I know
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified that testnet exists with a successful upload: https://ipfs.web4.testnet.page/ipfs/bafybeibe63hqugbqr4writdxgezgl5swgujay6t5uptw2px7q63r7crk2q/
Following a suggestion here
This introduces script, and adjusts the existing publish workflow. The script creates car, uploads car, then saves this cid to the package.json in under
nearfs.cid
(you can see one now, I tested and pushed the result to prove a working script)It also creates an asset-manifest.json during webpack build to make finding the main and runtime bundle hashes easier.
Successfully deployed to: https://ipfs.web4.near.page/ipfs/bafybeiftqwg2qdfhjwuxt5cjvvsxflp6ghhwgz5db3i4tqipocvyzhn2bq/