-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add IPFS service that is peered to https://ipfs.network.thegraph.com/ipfs/ #20
Comments
Hi Simon, |
Oh, that's bad. Thanks for the update. Shall we leave this issue open to investigate other options at a later point? Otherwise, feel free to close it. |
What about this proposed fix? ipfs/kubo#4343 (comment) |
That one I shared is temporary (but seems it should work) until this one lands ipfs/kubo#6932 |
For context here would be the config to setup an IPFS node to peer with The Graph's hosted service IPFS node: https://docs.ipfs.tech/how-to/peering-with-content-providers/#content-provider-list (thanks to Leo) |
|
I've seen reports that the flag doesn't stop it from net scanning. I'm willing to try it out but I need someone with a burner account that can afford to have their (baremetal) server (potentially) blocked in case this doesn't work. |
I think flag ipfs:
image: ipfs/kubo:v0.18.1
container_name: ipfs
restart: unless-stopped
environment:
IPFS_PROFILE: server
expose:
- 5001
volumes:
- ipfs_data:/data/ipfs
- ./ipfs-init.sh:/container-init.d/ipfs-init.sh
networks:
- monitor-net |
Currently, there is a single point of failure with https://ipfs.network.thegraph.com/ipfs/. Indexers should run their own node and peer to https://ipfs.network.thegraph.com/ipfs/ to increase resilience.
The text was updated successfully, but these errors were encountered: