cascade/ipfs-cluster
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Rename links to use the ipfscluster.io domain

Browse Source
This commit is contained in:
Hector Sanjuan 2022-06-15 11:30:23 +02:00
parent 508791b547
commit d7107791ed
6 changed files with 19 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
CHANGELOG.md
View File

@ -877,7 +877,7 @@ a certain size, both configurable.
Additionally, improvements to timeout behaviours have been introduced. Additionally, improvements to timeout behaviours have been introduced.
For more details, check the list below and the latest documentation on the For more details, check the list below and the latest documentation on the
[website](https://cluster.ipfs.io). [website](https://ipfscluster.io).
#### List of changes #### List of changes
@ -1186,7 +1186,7 @@ NAT-traversal and connectivity etc.
Users planning to setup public collaborative clusters should upgrade to this Users planning to setup public collaborative clusters should upgrade to this
release, which improves the user experience and comes with documentation on release, which improves the user experience and comes with documentation on
how to setup and join these clusters how to setup and join these clusters
(https://cluster.ipfs.io/documentation/collaborative). (https://ipfscluster.io/documentation/collaborative).
#### List of changes #### List of changes
@ -2138,7 +2138,7 @@ IPFS Cluster version 0.5.0 is a minor release which includes a major feature: **
This functionality is provided by `ipfs-cluster-ctl add` and by the API endpoint `/add`. The upload format (multipart) is similar to the IPFS `/add` endpoint, as well as the options (chunker, layout...). Cluster `add` generates the same DAG as `ipfs add` would, but it sends the added blocks directly to their allocations, pinning them on completion. The pin happens very quickly, as content is already locally available in the allocated peers. This functionality is provided by `ipfs-cluster-ctl add` and by the API endpoint `/add`. The upload format (multipart) is similar to the IPFS `/add` endpoint, as well as the options (chunker, layout...). Cluster `add` generates the same DAG as `ipfs add` would, but it sends the added blocks directly to their allocations, pinning them on completion. The pin happens very quickly, as content is already locally available in the allocated peers.
The release also includes most of the needed code for the [Sharding feature](https://cluster.ipfs.io/developer/rfcs/dag-sharding-rfc/), but it is not yet usable/enabled, pending features from go-ipfs. The release also includes most of the needed code for the [Sharding feature](https://ipfscluster.io/developer/rfcs/dag-sharding-rfc/), but it is not yet usable/enabled, pending features from go-ipfs.
The 0.5.0 release additionally includes a new experimental PinTracker implementation: the `stateless` pin tracker. The stateless pin tracker relies on the IPFS pinset and the cluster state to keep track of pins, rather than keeping an in-memory copy of the cluster pinset, thus reducing the memory usage when having huge pinsets. It can be enabled with `ipfs-cluster-service daemon --pintracker stateless`. The 0.5.0 release additionally includes a new experimental PinTracker implementation: the `stateless` pin tracker. The stateless pin tracker relies on the IPFS pinset and the cluster state to keep track of pins, rather than keeping an in-memory copy of the cluster pinset, thus reducing the memory usage when having huge pinsets. It can be enabled with `ipfs-cluster-service daemon --pintracker stateless`.
@ -2208,7 +2208,7 @@ As noted above, upgrade to `state` format version 5 is needed before starting th
#### Summary #### Summary
The IPFS Cluster version 0.4.0 includes breaking changes and a considerable number of new features causing them. The documentation (particularly that affecting the configuration and startup of peers) has been updated accordingly in https://cluster.ipfs.io . Be sure to also read it if you are upgrading. The IPFS Cluster version 0.4.0 includes breaking changes and a considerable number of new features causing them. The documentation (particularly that affecting the configuration and startup of peers) has been updated accordingly in https://ipfscluster.io . Be sure to also read it if you are upgrading.
There are four main developments in this release: There are four main developments in this release:
@ -2216,7 +2216,7 @@ There are four main developments in this release:
* Improvements to the `pintracker`: our pin tracker is now able to cancel ongoing pins when receiving an unpin request for the same CID, and vice-versa. It will also optimize multiple pin requests (by only queuing and triggering them once) and can now report * Improvements to the `pintracker`: our pin tracker is now able to cancel ongoing pins when receiving an unpin request for the same CID, and vice-versa. It will also optimize multiple pin requests (by only queuing and triggering them once) and can now report
whether an item is pinning (a request to ipfs is ongoing) vs. pin-queued (waiting for a worker to perform the request to ipfs). whether an item is pinning (a request to ipfs is ongoing) vs. pin-queued (waiting for a worker to perform the request to ipfs).
* Broadcasting of monitoring metrics using PubSub: we have added a new `monitor` implementation that uses PubSub (rather than RPC broadcasting). With the upcoming improvements to PubSub this means that we can do efficient broadcasting of metrics while at the same time not requiring peers to have RPC permissions, which is preparing the ground for collaborative clusters. * Broadcasting of monitoring metrics using PubSub: we have added a new `monitor` implementation that uses PubSub (rather than RPC broadcasting). With the upcoming improvements to PubSub this means that we can do efficient broadcasting of metrics while at the same time not requiring peers to have RPC permissions, which is preparing the ground for collaborative clusters.
* We have launched the IPFS Cluster website: https://cluster.ipfs.io . We moved most of the documentation over there, expanded it and updated it. * We have launched the IPFS Cluster website: https://ipfscluster.io . We moved most of the documentation over there, expanded it and updated it.
#### List of changes #### List of changes

2
CONTRIBUTING.md
View File

@ -1,3 +1,3 @@
# Guidelines for contributing # Guidelines for contributing
Please see https://cluster.ipfs.io/developer/contribute . Please see https://ipfscluster.io/developer/contribute .

20
README.md
View File

@ -11,7 +11,7 @@
> Pinset orchestration for IPFS > Pinset orchestration for IPFS
<p align="center"> <p align="center">
<img src="https://cluster.ipfs.io/cluster/png/IPFS_Cluster_color_no_text.png" alt="logo" width="300" height="300" /> <img src="https://ipfscluster.io/cluster/png/IPFS_Cluster_color_no_text.png" alt="logo" width="300" height="300" />
</p> </p>
IPFS Cluster provides data orchestration across a swarm of IPFS daemons by allocating, replicating and tracking a global pinset distributed among multiple peers. IPFS Cluster provides data orchestration across a swarm of IPFS daemons by allocating, replicating and tracking a global pinset distributed among multiple peers.
@ -42,29 +42,29 @@ Please participate in the [IPFS Cluster user registry](https://docs.google.com/f
## Documentation ## Documentation
Please visit https://cluster.ipfs.io/documentation/ to access user documentation, guides and any other resources, including detailed **download** and **usage** instructions. Please visit https://ipfscluster.io/documentation/ to access user documentation, guides and any other resources, including detailed **download** and **usage** instructions.
## News & Roadmap ## News & Roadmap
We regularly post project updates to https://cluster.ipfs.io/news/ . We regularly post project updates to https://ipfscluster.io/news/ .
The most up-to-date *Roadmap* is available at https://cluster.ipfs.io/roadmap/ . The most up-to-date *Roadmap* is available at https://ipfscluster.io/roadmap/ .
## Install ## Install
Instructions for different installation methods (including from source) are available at https://cluster.ipfs.io/download . Instructions for different installation methods (including from source) are available at https://ipfscluster.io/download .
## Usage ## Usage
Extensive usage information is provided at https://cluster.ipfs.io/documentation/ , including: Extensive usage information is provided at https://ipfscluster.io/documentation/ , including:
* [Docs for `ipfs-cluster-service`](https://cluster.ipfs.io/documentation/reference/service/) * [Docs for `ipfs-cluster-service`](https://ipfscluster.io/documentation/reference/service/)
* [Docs for `ipfs-cluster-ctl`](https://cluster.ipfs.io/documentation/reference/ctl/) * [Docs for `ipfs-cluster-ctl`](https://ipfscluster.io/documentation/reference/ctl/)
* [Docs for `ipfs-cluster-follow`](https://cluster.ipfs.io/documentation/reference/follow/) * [Docs for `ipfs-cluster-follow`](https://ipfscluster.io/documentation/reference/follow/)
## Contribute ## Contribute
PRs accepted. As part of the IPFS project, we have some [contribution guidelines](https://cluster.ipfs.io/support/#contribution-guidelines). PRs accepted. As part of the IPFS project, we have some [contribution guidelines](https://ipfscluster.io/support/#contribution-guidelines).
## License ## License

2
cmd/ipfs-cluster-ctl/dist/README.md vendored
View File

@ -14,4 +14,4 @@ $ ipfs-cluster-ctl --help
You can also obtain command-specific help with `ipfs-cluster-ctl help [cmd]`. The (`--host`) can be used to talk to any remote cluster peer (`localhost` is used by default). You can also obtain command-specific help with `ipfs-cluster-ctl help [cmd]`. The (`--host`) can be used to talk to any remote cluster peer (`localhost` is used by default).
For more information, please check the [Documentation](https://cluster.ipfs.io/documentation), in particular the [`ipfs-cluster-ctl` section](https://cluster.ipfs.io/documentation/ipfs-cluster-ctl). For more information, please check the [Documentation](https://ipfscluster.io/documentation), in particular the [`ipfs-cluster-ctl` section](https://ipfscluster.io/documentation/ipfs-cluster-ctl).

2
cmd/ipfs-cluster-follow/dist/README.md vendored
View File

@ -28,6 +28,6 @@ $ ipfs-cluster-follow <clusterName> run --help
$ ipfs-cluster-follow <clusterName> list --help $ ipfs-cluster-follow <clusterName> list --help
``` ```
For more information, please check the [Documentation](https://cluster.ipfs.io/documentation), in particular the [`ipfs-cluster-follow` section](https://cluster.ipfs.io/documentation/ipfs-cluster-follow). For more information, please check the [Documentation](https://ipfscluster.io/documentation), in particular the [`ipfs-cluster-follow` section](https://ipfscluster.io/documentation/ipfs-cluster-follow).

2
cmd/ipfs-cluster-service/dist/README.md vendored
View File

@ -12,4 +12,4 @@ Usage information can be obtained with:
$ ipfs-cluster-service --help $ ipfs-cluster-service --help
``` ```
For more information, please check the [Documentation](https://cluster.ipfs.io/documentation), in particular the [`ipfs-cluster-service` section](https://cluster.ipfs.io/documentation/ipfs-cluster-service). For more information, please check the [Documentation](https://ipfscluster.io/documentation), in particular the [`ipfs-cluster-service` section](https://ipfscluster.io/documentation/ipfs-cluster-service).