feat: IPFS based p2p image distribution #490
Merged
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.
Motivation & Context:
IPFS is a great P2P content platform. We don't need any centralised servers to work with data. This PR adds support for using IPFS as the underlying storage for OpenRegistry. This opens the door for so many opportunities for how the end users use OpenRegistry, some of them can be:
Description:
This PR implements the
dfs.DFS
interface for the IPFS RPC API. Since theDFS
interface defines aMultipart
upload sequence, we upload the layer parts in memory & upload the final object at the end. This isn't quite multipart but it works. This does of course leads to higher memory consumption since layers are cached in-memory before they're uploaded.Types of Changes:
PR Checklist: