4ea830f74e
This adds a new cluster command: ipfs-cluster-follow. This command allows initializing and running follower peers as configured by a remote-source configuration. The command can list configured peers and obtain information for each of them. Peers are launched with the rest API listening on a local unix socket. The command can be run to list the items in the cluster pinset using this endpoint. Alternatively, if no socket is present, the peer will be assumed to be offline and the pin list will be directly read from the datastore. Cluster peers launched with this command (and their configurations) are compatible with ipfs-cluster-ctl and ipfs-cluster-service. We purposely do not support most configuration options here. Using ipfs-cluster-ctl or launching the peers using ipfs-cluster-service is always an option when the usecase deviates from that supported by ipfs-cluster-follow. Examples: $ ipfs-cluster-follow -> list configured peers $ ipfs-cluster-follow --help $ ipfs-cluster-follow <clusterName> init <url> $ ipfs-cluster-follow <clusterName> info $ ipfs-cluster-follow <clusterName> run $ ipfs-cluster-follow <clusterName> list
46 lines
671 B
Plaintext
46 lines
671 B
Plaintext
tag_annotation
|
|
coverage.out
|
|
cmd/ipfs-cluster-service/ipfs-cluster-service
|
|
cmd/ipfs-cluster-ctl/ipfs-cluster-ctl
|
|
cmd/ipfs-cluster-follow/ipfs-cluster-follow
|
|
sharness/lib/sharness
|
|
sharness/test-results
|
|
sharness/trash*
|
|
vendor/
|
|
|
|
|
|
raftFolderFromTest*
|
|
peerstore
|
|
shardTesting
|
|
compose
|
|
|
|
# Compiled Object files, Static and Dynamic libs (Shared Objects)
|
|
*.o
|
|
*.a
|
|
*.so
|
|
|
|
# Folders
|
|
_obj
|
|
_test
|
|
test/sharness/test-results
|
|
test/sharness/trash*
|
|
test/sharness/lib/sharness
|
|
test/sharness/.test_config
|
|
test/sharness/.test_ipfs
|
|
|
|
# Architecture specific extensions/prefixes
|
|
*.[568vq]
|
|
[568vq].out
|
|
|
|
*.cgo1.go
|
|
*.cgo2.c
|
|
_cgo_defun.c
|
|
_cgo_gotypes.go
|
|
_cgo_export.*
|
|
|
|
_testmain.go
|
|
|
|
*.exe
|
|
*.test
|
|
*.prof
|