chore(ci): additional pin to scaleway #107
Merged
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
lidel
commented
Mar 13, 2024
Comment on lines
+346
to
+347
| - name: Pin to Scaleway | ||
| if: ${{ steps.scaleway.outputs.existing-pin == '' }} |
There was a problem hiding this comment.
ℹ️ Skipping on any preexisting pins for the CID before pinning it again to avoid HTTP 409 error due to duplicate pin. It would often happen in main branch when ./dist output does not change (e.g. commits with docs edits).
Comment on lines
+23
to
+24
| <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/[email protected]/css/tachyons.min.css" integrity="sha256-MgEf5i1a74lVzhT+1R6mBbWCUeUaxC8sQTaN5GY+CoI=" crossorigin="anonymous"> | ||
| <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/[email protected]/ipfs.css" integrity="sha256-tlU/gvVvLjSbTOfSZyCzuQxY8QcmHPtJJ1oTXilA9gk=" crossorigin="anonymous"> |
There was a problem hiding this comment.
ℹ️ I needed to produce new ./dist for testing, so switched to SRI + jsdelivr here.
Comment on lines
+4
to
+18
| <!-- | ||
|
|
||
| This HTML page initializes IPFS Service Worker Gateway. | ||
|
|
||
| The HTTP server behind this HTTP URL does not host this website. | ||
| Instead, it sends basic website code along with JavaScript. The JS sets | ||
| up a tool called IPFS Service Worker Gateway in the user's browser and | ||
| uses JavaScript version of IPFS (https://helia.io/) to get IPFS blocks | ||
| from content providers. | ||
|
|
||
| CID hash verification and data assembly happens in the browser. | ||
|
|
||
| Learn more about it here: https://github.com/ipfs-shipyard/helia-service-worker-gateway | ||
|
|
||
| --> |
There was a problem hiding this comment.
ℹ️ @2color fysa added this disclaimer for curl/cli devs and users expecting deserialized payload, feel free to adjust in follow-up PR.
45 tasks
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.
Similar to #105, pins to
pl-waw.ipfs.labs.scw.cloudusing remote pinning API.Some thoughts on Scaleway as pinning service
--cidfiltering onipfs pin remotecommands does not work correctly, seems to be ignored by Scaleway.--nameworks, so just putting CID there to allow us skip pinning if CID is already pinned (example). 🤷Still, was easy to make it work, is fast, and gives us another copy.
I am going to merge this to increase our ability to dogfood setup with more than two pinning services.
Once merged, we will have three ways of pinning remotely, which is great for dogfooding, and evaluating complexity/maintenance/stability/cost:
ipfs-cluster-ctlCLIipfs pin remote/ pinning-services-api-spec