Open whizzzkid opened 1 year ago
I'm moving this back to ipfs-companion, as it does not seem to be actionable from the perspective of Kubo repository (imo Kubo repo should not have documentation related to companion, just like we don't have anything about ipfs-desktop, ipfsd-ctl, ipfs-cluster or any other project that uses Kubo – such docs belong to repo of respective project)
As for configuring Companion to work with non-localhost node, my suggestion is to be conservative:
:point_right: By looking at the reddit post, it sounds like what IPFS Companion could do, is to have more meaningful error message when non-localhost RPC or Gateway is used. It should explain security (CORS giving admin access to RPC API) and/or interop ramifications (non-localhost cleartext http://
gateway causing mixed-content errors IF subresources are redirected).
[..] shows ipfs not running even though I am using a kubo rpc install on the local network. #
This sounds like a bug?
How about add virtual network for API isolation. like through zerotier-like intranet for using api remotely, while local computer at same network, then put the other ports public if one-self wanted, which like gateway, swarm etc,.? maybe this way should link the cluster together in more safe way?
Checklist
Location
No response
Description
A few interesting points came up: https://www.reddit.com/r/ipfs/comments/145inx4/just_tried_ipfs_a_few_thoughts/
I believe we should cover possible scenarios and setup guides to make pairing companion with kubo easy.
relates to: