ipfs
Configurable Bootstrappers
Tracking issue to add a flag (and environment variable) to allow overriding the bootstrappers for private deployments: https://github.com/ipfs/rainbow/pull/111#discussion_r1577097959
I was looking into the documents and source code to see if this could be implemented with a private IPFS ntework. Seems like this might be the answer to that question?
@anthonyra iiuc to make Rainbow compatible with swarm.key-based private bitswap network you need more than just Bootstrappers.
:point_right: If you need PNET support, please fill a new issue describing your feature request (this one is only about configuration option for providing custom bootstrappers). :pray:
I actually just stumbled upon that this morning.. and I suppose when commenting earlier I wasn't 100% aware of how all the things are wired together. I'll be sure to create a feature request 👍🏻
I actually just stumbled upon that this morning
@anthonyra if you're not sure you want to use pnet/swarm keys feature (it has it's tradeoffs) you might want to start a discussion with people in the forums https://discuss.ipfs.tech/ or chat channels https://docs.ipfs.tech/community/#chat.
@aschmahmann I'm sort of working with what is currently being used. There's a project using PNET already along with ipfs-cluster and I'm trying to configure all the things for best performance and reliability on our end since we intend to host their service. I'm familiar with a "sentry" architecture to add protections and thought rainbow could be used as such for accessing the data from the service.