-
Notifications
You must be signed in to change notification settings - Fork 0
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
Spike: Self-Hosted Web3.Storage #1
Comments
Alan is going to add some additional notes, but this is effectively done. |
DEMO: https://youtu.be/eJVA97t-jaw?si=CL9BQCaRKZ15UHVb&t=2748 local.storage
local.freeway
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Goals
Time box to one week -- attempt to produce an upload node that can persist data and a retrieval node that can talk to each other on a local system
For this round, don't worry about web assembly -- feel free to run docker or whatever you like.
The goal here is to identify hidden dependencies on cloud services and/or assumptions that make portability difficult.
If this is trivially easy, that's wonderful news. The next move will be to seperate the upload node from the storage device -- and start building code to register storage nodes with the uploader and have it round robin content uploads between them.
The text was updated successfully, but these errors were encountered: