3 ms·
for my sites that expect an occasional burst of traffic, I moved all the media assets to IPFS and served by one of the gateway that functions as CDN for IPFS st
by vmception 4y ago
for my sites that expect an occasional burst of traffic, I moved all the media assets to IPFS and served by one of the gateway that functions as CDN for IPFS stuff.
this circumvents Netlify's bandwidth metering and all the users retrieving the IPFS assets keeps the IPFS assets loading quickly
- dvasdekis 4y agoHow did you do this? Is there a tutorial that you followed? I would love to do the same, potentially with Cloudflare further caching the IPFS-hosted files.
- vmception 4y agoAlthough Pinata offers a SaaS service where you pay them monthly to pin and they charge for bandwidth, web3.storage lets you pin 1 Tib for free and without bandwidth metering. So I pinned there, and then got the hash and found the gateway+cdn with low ping time and just concatenate the url, which I hardcode in the frontend note, I append ?filename=filename.extension to the url to keep track of which hash is what ironically Pinata is also a gateway that will show any hash for free then I just deploy the whole project/frontend/backend to github and that auto deploys to netlify and the domain name routes to that instance