4 ms·
Thanks for the article. After reading it, I went and added an IPFS node to my Kubernetes deployment on Google Cloud and then mapped the /ipfs and /ipns endpoint
by kordlessagain 9y ago
Thanks for the article. After reading it, I went and added an IPFS node to my Kubernetes deployment on Google Cloud and then mapped the /ipfs and /ipns endpoints through Kong so they would be served by https://api.wisdom.sh/<ipfs|ipns>/ https://api.wisdom.sh/<ipfs|ipns>/. This effectively gives people yet another domain they can use which doesn't require installing the IPFS client. Any IPFS site wil work through the proxy, but here's the site under discussion: https://api.wisdom.sh/ipns/QmZxWEBJBVkGDGaKdYPQUXX4KC5TCWbvuR4iYZrTML8XCR/en/index.html https://api.wisdom.sh/ipns/QmZxWEBJBVkGDGaKdYPQUXX4KC5TCWbvu...
If anyone wants the scripts I used to build up the system, let me know. Here's the Kubernetes YAML I used: https://gist.github.com/kordless/5625ae8abf3d3f14dd3f9c9d500c7b86 https://gist.github.com/kordless/5625ae8abf3d3f14dd3f9c9d500...
- HarfTarf 9y agohttps://ipfs.github.io/public-gateway-checker/ https://ipfs.github.io/public-gateway-checker/ It would be nice to add your gateway to the list.
- unkown-unknowns 9y agoIt took a very long time to load the page. Consider implementing some caching if you haven't already.
- kordlessagain 9y agoI think it's because the named version is being used (ipns) which may or may not be involving a lot of requests to the network to resolve (perhaps to the main node even). I've resolved and pinned the original content here: https://api.wisdom.sh/ipfs/QmXj5GjZ8WApwq79EyAeNZ2E6pQkJmbrjC84usQL24D41d/en/index.html https://api.wisdom.sh/ipfs/QmXj5GjZ8WApwq79EyAeNZ2E6pQkJmbrj...