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

/ipfs/cached + /ipfs/pinned fuse dirs #257

Open
jbenet opened this issue Nov 3, 2014 · 6 comments
Open

/ipfs/cached + /ipfs/pinned fuse dirs #257

jbenet opened this issue Nov 3, 2014 · 6 comments
Labels
help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature topic/fuse Topic fuse

Comments

@jbenet
Copy link
Member

jbenet commented Nov 3, 2014

would be nice to list the hashes stored locally under /ipfs with special (well known) directories:

  • /ipfs/pinned for all hashes pinned locally
  • /ipfs/cached for all hashes available locally, and not pinned.
  • /ipfs/local all hashes available locally (pinned U cached)
@jbenet jbenet added kind/enhancement A net-new feature or improvement to an existing feature help wanted Seeking public contribution on this issue labels Nov 3, 2014
@ebuchman
Copy link
Contributor

ebuchman commented Nov 3, 2014

How best to track cached (non pinned) objects?

  • KeyList() (overheard probably too high)
  • index file (is the cache flushed? if files are not pinned, will we drop them? if so this may stay small and possible advantage of human readable, otherwise probably no good)
  • datastore query (with something like index/<tree#>)

@jbenet
Copy link
Member Author

jbenet commented Jan 8, 2015

To go along with the fuse files, we should also have a command. maybe it's just an extension of refs

# outputs all refs stored locally
ipfs refs local 

# outputs only the pinned
ipfs refs --pinned

# complement
ipfs refs --cached

@jbenet
Copy link
Member Author

jbenet commented Jan 15, 2015

Update: this is possible to implement now. the blockstore has {AllKeys, AllKeysChan} functions

@jbenet jbenet added the topic/fuse Topic fuse label Mar 28, 2015
@whyrusleeping
Copy link
Member

Further update:
I want to have every ipfs add make an entry in the files api space, maybe under /pins or something. With that implemented, we could almost (except for the advent of direct pins) remove pinning entirely, and replace it with 'copying to your local filesystem' which is an idea i really like.

@daviddias
Copy link
Member

👍 to this idea (and also making files add a thing)

@whyrusleeping
Copy link
Member

in the future, we may even move ipfs add to ipfs files add. This would help with separating the ideas of DAG and unixfs better than we are now.

@daviddias daviddias removed the icebox label Jan 2, 2016
ariescodescream pushed a commit to ariescodescream/go-ipfs that referenced this issue Oct 23, 2021
Fixes race conditions in the tests when using go modules.
@aschmahmann aschmahmann mentioned this issue Dec 1, 2021
80 tasks
@ajnavarro ajnavarro mentioned this issue Aug 24, 2022
72 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature topic/fuse Topic fuse
Projects
None yet
Development

No branches or pull requests

5 participants