531379b1d9
* add ipv6 listening addresses to the default config * ipfsproxy: support multiple listeners. Add default ipv6. * mm * restapi: support multiple listen addresses. enable ipv6 * cluster_config: format default listen addresses * commands: update for multiple listeners. Fix randomports for udp and ipv6. * ipfs-cluster-service: fix randomports test * multiple listeners: fix remaining tests * golint * Disable ipv6 in defaults It is not supported by docker by default. It is not supported in travis-CI build environments. User can enable it now manually. * proxy: disable ipv6 in test * ipfshttp: fix test Co-authored-by: @RubenKelevra <cyrond@gmail.com> |
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| adder | ||
| allocator | ||
| api | ||
| cmd | ||
| cmdutils | ||
| config | ||
| consensus | ||
| datastore | ||
| docker | ||
| informer | ||
| ipfsconn/ipfshttp | ||
| monitor | ||
| observations | ||
| pintracker | ||
| pstoremgr | ||
| rpcutil | ||
| sharness | ||
| state | ||
| test | ||
| version | ||
| .codeclimate.yml | ||
| .codecov.yml | ||
| .dockerignore | ||
| .gitignore | ||
| .travis.yml | ||
| add_test.go | ||
| allocate.go | ||
| CHANGELOG.md | ||
| cluster_config_test.go | ||
| cluster_config.go | ||
| cluster_test.go | ||
| cluster.go | ||
| clusterhost.go | ||
| config_test.go | ||
| connect_graph.go | ||
| CONTRIBUTING.md | ||
| COPYRIGHT | ||
| docker-compose.yml | ||
| Dockerfile | ||
| Dockerfile-bundle | ||
| Dockerfile-test | ||
| go.mod | ||
| go.sum | ||
| ipfscluster_test.go | ||
| ipfscluster.go | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| logging.go | ||
| Makefile | ||
| peer_manager_test.go | ||
| pnet_test.go | ||
| README.md | ||
| release.sh | ||
| rpc_api.go | ||
| rpc_policy.go | ||
| util.go | ||
IPFS Cluster
Automated data availability and redundancy on IPFS
IPFS Cluster provides data orchestration across a swarm of IPFS daemons by allocating, replicating and tracking a global pinset distributed among multiple peers.
It provides:
- A cluster peer application:
ipfs-cluster-service, to be run along withgo-ipfs. - A client CLI application:
ipfs-cluster-ctl, which allows easily interacting with the peer's HTTP API. - An additional "follower" peer application:
ipfs-cluster-follow, focused on simplifying the process of configuring and running follower peers.
Are you using IPFS Cluster?
Please participate in the IPFS Cluster user registry.
Table of Contents
Documentation
Please visit https://cluster.ipfs.io/documentation/ to access user documentation, guides and any other resources, including detailed download and usage instructions.
News & Roadmap
We regularly post project updates to https://cluster.ipfs.io/news/ .
The most up-to-date Roadmap is available at https://cluster.ipfs.io/roadmap/ .
Install
Instructions for different installation methods (including from source) are available at https://cluster.ipfs.io/download .
Usage
Extensive usage information is provided at https://cluster.ipfs.io/documentation/ , including:
Contribute
PRs accepted. As part of the IPFS project, we have some contribution guidelines.
License
This library is dual-licensed under Apache 2.0 and MIT terms.
© 2020. Protocol Labs, Inc.