Skip to content

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

Open

Description

@jbenet

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)

Activity

  1. added
    kind/enhancementA net-new feature or improvement to an existing feature
    help wantedSeeking public contribution on this issue
    on Nov 3, 2014
  2. ebuchman commented on Nov 3, 2014

    @ebuchman
    Contributor

    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#>)
  3. jbenet commented on Jan 8, 2015

    @jbenet
    MemberAuthor

    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
  4. jbenet commented on Jan 15, 2015

    @jbenet
    MemberAuthor

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

  5. whyrusleeping commented on Jan 1, 2016

    @whyrusleeping
    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.

  6. daviddias commented on Jan 1, 2016

    @daviddias
    Member

    πŸ‘ to this idea (and also making files add a thing)

  7. whyrusleeping commented on Jan 1, 2016

    @whyrusleeping
    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedSeeking public contribution on this issuekind/enhancementA net-new feature or improvement to an existing featuretopic/fuseTopic fuse

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions