Support local=true as a configurable option for the proxy endpoints (:9095)

[rryter]

Hello 😄

As per discussion, the rest api /add endpoint (:9094) supports the setting local=true.

This will just add on the node receiving the request (and not all nodes at the same time), and cluster-pin when finished. The rest of the nodes will copy the content via pubsub, much faster.

We would like to run a public IPFS-Cluster and therefore plan to allow users to use the IPFS-Proxy API (:9095).

It would be awesome if the setting "local=true" would be a configurable option.
I assume the default would be local=false but we could set it to true for our cluster.

Does that make sense?

I'm new to IPFS / IPFS-Cluster so I don't know if this would be applicable to other enpoints too?

👋

[hsanjuan]

hi @sergeiudris , go ahead! thanks!

[hsanjuan]

oh, it's true... it's done already because the code path is the same.

creates BlockAdder with empty dests ( []peer.ID{""} )

No, dests are not empty. It has 1 dest, which is "". This is the local peer. The BlockPut rpc calls get executed in the same peer (bypassing the rpc request/response - this is in go-libp2p-gorpc).

In the end adding "locally" is the equivalent of adding with 1 destination. I think the codepaths there are hopefully well-tested (and tried).

Thanks a lot for looking into this, though. Probably best to spend time on some of the other open issues. I'm very sorry that I did not realize this was there already.