Skip to content
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

IPNS mount, <MISSING> writing a file being fetched to the mount point #5209

Open
kvm2116 opened this issue Jul 9, 2018 · 1 comment
Open

Comments

@kvm2116
Copy link
Contributor

kvm2116 commented Jul 9, 2018

Version information:

Type:

Bug

Description:

I have made some progress in fixing the bugs in IPNS mount. Specifically, as far as I know, there are two issues currently:

  1. IPNS address is not resolved correctly.
  2. The files being fetched from peers through the mount point are not written to the IPNS mount point.

For the first issue, I was able to identify and fix the issue. I will create a pull request so that the fix can be incorporated.

For the second issue, I am not sure how to implement it.
I would think the following to be the desired behavior of the IPNS mount point:

  1. When a directory/file/tar is fetched from peers through the IPNS mount point, the file should be written under a new directory, whose name is that of peer-id (/ipns/PEER_ID/directory>.
  2. This directory/file/tar should have the option to be edited locally. For example, if it is a directory, new files can be added or old files can be deleted. If it is a file, the user should be able to make changes locally to the file.

Any thoughts on how this should be implemented?

@djdv
Copy link
Contributor

djdv commented May 14, 2019

I've been working on a new variant of the ipfs mount command.
Discussion about it is taking place in #5003 and
ipfs/interface-go-ipfs-core#30

The interface is still a WIP but if I understand this correctly it should allow you to implement a mountpoint that behaves in the way you listed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants