You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what the bug is.
12
+
13
+
**To Reproduce**
14
+
Steps to reproduce the behavior.
15
+
16
+
**Expected Behavior**
17
+
What did you expect to happen?
18
+
19
+
** OS **
20
+
21
+
** Node version **
22
+
23
+
** Was the daemon installed from NPM or bundled with Beaker? **
24
+
25
+
Add any other context about the problem here.
26
+
27
+
__Important Note__: Daemon errors are likely to be found in `~/.hyperdrive/log.json` or `~/.hyperdrive/output.log` (the latter is for unexpected, non-JSON output). These files might contain sensitive drive keys, so don't upload the whole thing -- just extract any stack traces or odd error messages!
Copy file name to clipboardExpand all lines: README.md
+64-4Lines changed: 64 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,9 @@ The client exposes a gRPC interface for a) creating and interacting with remote
25
25
Check out the [daemon tests](https://github.com/andrewosh/hyperdrive-daemon/blob/hyperdrive-api/test/hyperdrive.js) for more example usage.
26
26
27
27
### Hyperdrive
28
-
The client's Hyperdrive API is designed to mirror the methods in Hyperdrive as closely as possible.
28
+
The client's Hyperdrive API is designed to mirror the methods in Hyperdrive as closely as possible.
29
+
30
+
All drive commands can be found through the `client.drives` object.
29
31
30
32
#### General Operations
31
33
Operations to manage sessions or get more general information about the state of the daemon.
@@ -101,7 +103,9 @@ Method arguments take the same form as those in Hyperdrive. The following method
101
103
20.`drive.checkout(version)` // Returns a new `RemoteHyperdrive` instance for the checkout.
102
104
103
105
### FUSE
104
-
The client library also provides programmatic access to the daemon's FUSE interface. You can mount/unmount your root drive, or mount and share subdrives:
106
+
The client library also provides programmatic access to the daemon's FUSE interface.
107
+
108
+
All FUSE commands can be found on the `client.fuse` object.
105
109
106
110
##### `client.fuse.mount(mnt, opts, cb)`
107
111
Mount either the root drive (if `/mnt` is not specified), or a subdirectory within the root drive.
@@ -112,10 +116,66 @@ Mount either the root drive (if `/mnt` is not specified), or a subdirectory with
112
116
Unmounts either a subdrive, or the root drive if `mnt` is not specified.
113
117
114
118
##### `client.fuse.publish(path, cb)`
115
-
Advertise the drive mounted at `path` to the network.
119
+
Advertise the drive mounted at `path` to the swarm.
116
120
117
121
##### `client.fuse.unpublish(path, cb)`
118
-
Stop advertisingthe drive mounted at `path` to the network.
122
+
Stop advertising the drive mounted at `path` to the swarm.
123
+
124
+
### Peersockets
125
+
`client.peersockets` lets your directly exchange messages with connected peers. You can discover all peers swarming a given discovery key using the peers API (`client.peers`) described below.
126
+
127
+
Peers are all identified by aliases in order to reduce bandwidth consumtion, as the alternative is to attach NOISE keys to every message. Aliases can be mapped to/from NOISE keys through the `client.peers` API.
0 commit comments