Mount IPFS as writable filesystem? #64
Comments
|
have you tried doing the thing you suggest? |
|
Ha, I just noticed: ipfs/kubo#1007 This is awesome! Sorry for the frivolous question; I could have investigated this more myself before posting. |
|
@dpercy haha, no worries! i'm glad this is a feature people still want 👍 (warning though, i havent looked at that code in a good while and travis CI cant test fuse stuff for us) |
|
Is it possible for more than one node to write to the same directory? I guess they would need to both have access to the same private key to update the ipns entry. Is it possible to run IPFS nodes with identical keys on two separate machines? |
|
that is planned, but not yet implemented. Its gonna be tricky to do right. |
|
This issue has been moved to https://discuss.ipfs.io/t/mount-ipfs-as-writable-filesystem/439. |
|
Can the IPFS team please lock all GitHub issues that have been moved elsewhere? |
|
Why -- is IPFS finished? Is everything complete and good to go? I would imagine we want to leave as many channels open as possible |
Because this discussion has been moved here https://discuss.ipfs.io/t/mount-ipfs-as-writable-filesystem/439 |
Currently if you want to write a file to IPFS you have to do so explicitly, with either the command-line interface or the HTTP gateway. By contrast, reading files works transparently when you mount /ipfs and /ipns.
Will there be a way to transparently write files to IPFS through its mount point? For example, suppose I wanted to use
/ipns/<hash-of-pubkey>as a personal Dropbox. I want to be able tocd /ipns/<hash-of-pubkey> ; echo "hello new file" > file.txt, and then have/ipns/<hash-of-pubkey>/file.txtbecome visible to other nodes. Will an interface like this be a core feature of IPFS, or should this be a separate FUSE application written on top of IPFS?The text was updated successfully, but these errors were encountered: