To spawn nodes from browsers, first start an ipfsd-ctl server from node.js and make the address known to the browser (the default way is to set process.env.IPFSD_CTL_SERVER in your bundle):
Example: Create server
In node.js:
// Start a remote disposable node, and get access to the api // print the node id, and stop the temporary daemon
ipfsd-ctl can spawn disposable and non-disposable nodes.
disposable- Disposable nodes are useful for tests or other temporary use cases, they create a temporary repo which is deleted automatically when the node is stopped
non-disposable - Disposable nodes will not delete their repo when stopped
This module allows you to spawn long-lived IPFS implementations from any JS environment and interact with the as is they were in the local process.
It is designed mostly for testing interoperability and is not suitable for production use.
Spawning a single noder:
createNode
Example: Spawning a Kubo node
Manage multiple nodes:
createFactory
Use a factory to spawn multiple nodes based on some common template.
Example: Spawning multiple Kubo nodes
Override config based on implementation type
createFactory
takes a second argument that can be used to pass default options to an implementation based on thetype
field.Spawning nodes from browsers
To spawn nodes from browsers, first start an ipfsd-ctl server from node.js and make the address known to the browser (the default way is to set
process.env.IPFSD_CTL_SERVER
in your bundle):Example: Create server
In node.js:
In a browser:
Disposable vs non Disposable nodes
ipfsd-ctl
can spawndisposable
andnon-disposable
nodes.disposable
- Disposable nodes are useful for tests or other temporary use cases, they create a temporary repo which is deleted automatically when the node is stoppednon-disposable
- Disposable nodes will not delete their repo when stopped