Implementation of the IPFS repo spec (https://github.com/ipfs/specs/blob/master/REPO.md) in JavaScript
This is the implementation of the IPFS repo spec in JavaScript.
- Background
- Install
- Usage
- API
- Setup
- Repos
- Blocks
Promise<Block> repo.blocks.put(block:Block)
AsyncIterator<Block> repo.blocks.putMany(source:AsyncIterable<Block>)
Promise<Block> repo.blocks.get(cid:CID)
AsyncIterable<Block> repo.blocks.getMany(source:AsyncIterable<CID>)
Promise<boolean> repo.blocks.has (cid:CID)
Promise<boolean> repo.blocks.delete (cid:CID)
AsyncIterator<Block|CID> repo.blocks.query (query)
Promise<CID> repo.blocks.delete(cid:CID)
AsyncIterator<CID> repo.blocks.deleteMany(source:AsyncIterable<CID>)
- Datastore
- Config
- Version
- API Addr
- Status
- Lock
- Notes
- Contribute
- License
Here is the architectural reasoning for this repo:
┌────────────────────────────────────────┐
│ IPFSRepo │
└────────────────────────────────────────┘
┌─────────────────┐
│ / │
├─────────────────┤
│ Datastore │
└─────────────────┘
┌───────────┴───────────┐
┌─────────────────┐ ┌─────────────────┐
│ /blocks │ │ /datastore │
├─────────────────┤ ├─────────────────┤
│ Datastore │ │ LevelDatastore │
└─────────────────┘ └─────────────────┘
┌────────────────────────────────────────┐ ┌────────────────────────────────────────┐
│ IPFSRepo - Default Node.js │ │ IPFSRepo - Default Browser │
└────────────────────────────────────────┘ └────────────────────────────────────────┘
┌─────────────────┐ ┌─────────────────┐
│ / │ │ / │
├─────────────────┤ ├─────────────────┤
│ FsDatastore │ │ IdbDatastore │
└─────────────────┘ └─────────────────┘
┌───────────┴───────────┐ ┌───────────┴───────────┐
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ /blocks │ │ /datastore │ │ /blocks │ │ /datastore │
├─────────────────┤ ├─────────────────┤ ├─────────────────┤ ├─────────────────┤
│ FlatfsDatastore │ │LevelDBDatastore │ │ IdbDatastore │ │ IdbDatastore │
└─────────────────┘ └─────────────────┘ └─────────────────┘ └─────────────────┘
This provides a well defined interface for creating and interacting with an IPFS repo.
> npm install ipfs-repo
var IPFSRepo = require('ipfs-repo')
var IPFSRepo = require('ipfs-repo')
Loading this module through a script tag will make the IpfsRepo
obj available in the global namespace.
<script src="https://unpkg.com/ipfs-repo/dist/index.min.js"></script>
<!-- OR -->
<script src="https://unpkg.com/ipfs-repo/dist/index.js"></script>
Example:
const Repo = require('ipfs-repo')
const repo = new Repo('/tmp/ipfs-repo')
await repo.init({ cool: 'config' })
await repo.open()
console.log('repo is ready')
This now has created the following structure, either on disk or as an in memory representation:
├── blocks
│ ├── SHARDING
│ └── _README
├── config
├── datastore
├── keys
└── version
Creates an IPFS Repo.
Arguments:
path
(string, mandatory): the path for this repooptions
(object, optional): may contain the following valuesautoMigrate
(bool, defaults totrue
): controls automatic migrations of repository.onMigrationProgress
(function(version, percentComplete, message)): callback function to be notified of migration progresslock
(Lock or string Deprecated): what type of lock to use. Lock has to be acquired when opening. string can be"fs"
or"memory"
.storageBackends
(object, optional): may contain the following values, which should each be a class implementing the datastore interface:root
(defaults todatastore-fs
in Node.js anddatastore-level
in the browser). Defines the back-end type used for gets and puts of values at the root (repo.set()
,repo.get()
)blocks
(defaults todatastore-fs
in Node.js anddatastore-level
in the browser). Defines the back-end type used for gets and puts of values atrepo.blocks
.keys
(defaults todatastore-fs
in Node.js anddatastore-level
in the browser). Defines the back-end type used for gets and puts of encrypted keys atrepo.keys
datastore
(defaults todatastore-level
). Defines the back-end type used as the key-value store used for gets and puts of values atrepo.datastore
.
const repo = new Repo('path/to/repo')
Creates the necessary folder structure inside the repo
Locks the repo to prevent conflicts arising from simultaneous access
Unlocks the repo.
Tells whether this repo exists or not. Returned promise resolves to a boolean
The returned promise resolves to false
if the repo has not been initialized and true
if it has
Root repo:
Put a value at the root of the repo
key
can be a Uint8Array, a string or a Key
Get a value at the root of the repo
key
can be a Uint8Array, a string or a Key
block
should be of type Block
Put many blocks.
source
should be an AsyncIterable that yields entries of type Block
Get block.
cid
is the content id of type CID
Get many blocks
source
should be an AsyncIterable that yields entries of type CID
Indicate if a block is present for the passed CID
cid
should be of the type CID
Deletes a block
cid
should be of the type CID
Query what blocks are available in blockstore.
If query.keysOnly
is true, the returned iterator will yield CIDs, otherwise it will yield Blocks
query
is a object as specified in interface-datastore.
Datastore:
cid
should be of the type CID
Delete a block
source
should be an Iterable or AsyncIterable that yields entries of the type CID
Delete many blocks
This contains a full implementation of the interface-datastore
API.
Instead of using repo.set('config')
this exposes an API that allows you to set and get a decoded config object, as well as, in a safe manner, change any of the config values individually.
Set a config value. value
can be any object that is serializable to JSON.
key
is a string specifying the object path. Example:
await repo.config.set('a.b.c', 'c value')
const config = await repo.config.get()
assert.equal(config.a.b.c, 'c value')
Set the whole config value. value
can be any object that is serializable to JSON.
Get a config value. Returned promise resolves to the same type that was set before.
key
is a string specifying the object path. Example:
const value = await repo.config.get('a.b.c')
console.log('config.a.b.c = ', value)
Get the entire config value.
Whether the config sub-repo exists.
Gets the repo version (an integer).
Sets the repo version
Gets the API address.
Sets the API address.
value
should be a Multiaddr or a String representing a valid one.
Gets the repo status.
Returned promise resolves to an Object
with the following keys:
numObjects
repoPath
repoSize
version
storageMax
IPFS Repo comes with two built in locks: memory and fs. These can be imported via the following:
const fsLock = require('ipfs-repo/src/lock') // Default in Node.js
const memoryLock = require('ipfs-repo/src/lock-memory') // Default in browser
You can also provide your own custom Lock. It must be an object with the following interface:
Sets the lock if one does not already exist. If a lock already exists, should throw an error.
dir
is a string to the directory the lock should be created at. The repo typically creates the lock at its root.
Returns closer
, where closer
has a close
method for removing the lock.
Closes the lock created by lock.open
If no error was thrown, the lock was successfully removed.
Checks the existence of the lock.
dir
is the path to the directory to check for the lock. The repo typically checks for the lock at its root.
Returned promise resolves to a boolean
indicating the existence of the lock.
When there is a new repo migration and the version of the repo is increased, don't
forget to propagate the changes into the test repo (test/test-repo
).
For tools that run mainly in the browser environment, be aware that disabling automatic migrations leaves the user with no way to run the migrations because there is no CLI in the browser. In such a case, you should provide a way to trigger migrations manually.
There are some ways you can make this module better:
- Consult our open issues and take on one of them
- Help our tests reach 100% coverage!
This repository falls under the IPFS Code of Conduct.