Manage multiple dat instances in multiple locations.
var Multidat =var toilet =var db =
If there is an error initializing a dat, instead of the whole process failing, an error object with attached
.dir property will be pushed into the list of dats instead. That means when consuming
multidat.list(), you should check for errors:
var dats = multidatdats
This way you can decide for yourself whether an individual initialization failure should cause the whole process to fail or not.
Multidat(db, opts, callback(err, multidat))
Creat a new Multidat instance. Takes a
toiletdb instance and a callback.
Dat: Use provided dat factory instead of dat-node
multidat.create(dir, opts, callback(err, dat))
Create a new
dats = multidat.list()
List all available
Close and remove a
multidat.readManifest(dat, callback(err, manifest))
dat.json file from the
dat archive. This method is expected to be
dat archives provide a built-in method to return archives.
This package exists to manage multiple
dat archives in different directories.
The dat-node package is mostly stateless; all state is persisted
into the archives themselves. This package acts as a layer on top to keep track
of where archives are located and manage them between sessions.
When not to use this
If you're running a server, it's usually enough to run mafintosh/hypercore-archiver which is more consistent and simpler. If you're building a tool that only needs to manage a single dat archive at the time it's recommended to use datproject/dat-node instead.