From 9dedc410359132dc027b812426ff15652638f5ab Mon Sep 17 00:00:00 2001 From: jzakotnik Date: Fri, 3 Jan 2025 13:13:30 +0100 Subject: [PATCH] updated debug argument to get to the HTTP API calls --- content/documentation/guides/pinning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/documentation/guides/pinning.md b/content/documentation/guides/pinning.md index 0184366..63e692d 100644 --- a/content/documentation/guides/pinning.md +++ b/content/documentation/guides/pinning.md @@ -11,7 +11,7 @@ Cluster usage mostly consists of adding and removing pins. This is usually perfo When working with a large number of pins, it is important to keep an eye on the state of the pinset, whether every pin is getting correctly pinned an allocated. This section provides in-depth explanations on how pinning works and the different operations that a cluster peer can perform to simplify and maintain the cluster pinsets. -
For clarity, we use ipfs-cluster-ctl commands, but every one of them is using an HTTP REST API endpoint from the cluster peer, so all commands can be performed directly against the API.
+
For clarity, we use ipfs-cluster-ctl commands, but every one of them is using an HTTP REST API endpoint from the cluster peer, so all commands can be performed directly against the API. If you add the --debug argument, you can inspect the respective HTTP REST API calls being performed.
* [Adding files](#adding-files) * [Pinning CIDs](#pinning-cids)