10 ms·
Show HN: IPFS-Deploy – Zero-Config CLI to Deploy Static Websites to IPFS
- agentofuser 7y agoHi! Author here. This is my first npm package, so I'd love to hear feedback on how I can improve it, what tools I can use for that, etc. Thank you for checking it out :)
- restwell 7y agoIs it possible to update a website hosted on IPFS and push those changes to all IPFS users? The equivalent on AWS Cloudfront would be breaking the cache, so all users would see the most recent version. I'm not sure if this would work on IPFS because it seems more like a P2P network and there might be many different (and old) versions of the site at different locations in the system, with no way of controlling who sees what.
- icebraining 7y agoNot an expert, but: IPFS is p2p, but all the content is accessed only by a hash, so the same address always refers to the same version; when you update the site, you're actually creating a new address, leaving the old untouched. Using Cloudflare, you can tie a regular domain to one of these addresses, but that "tie" is only stored there, so when you push a new version, you can update the Cloudflare settings, and everyone connecting to the domain will see the new version "immediately", even if the old version still exists in the p2p network.
- totony 7y agoipfs has its own mutable content adressing named IPNS
- bravura 7y agoWith IPFS what are the costs to keep your site live?
- theamk 7y agoIt is like torrent, so you need to have a seeder node all the time - it is called “pinning” in IPFS. There is a number of services, the price seems to be around $0.3/(gb*month)
- gitgud 7y agoHow does that compare with AWS? Is IPFS worth using for a CDN? (apologies for the acronyms...)
- neiman 7y agoAWS and IPFS are so different that you can't compare then. I'd say that the right comparison of IPFS is to BitTorrent.
- jononor 7y agoIf I am supposed to host my website on it, I want to know how much it would cost (for a given service level). Don't really care if the tech is more like butterflies or turtles...
- blotter_paper 7y agoIPFS nodes generally cache data that has been accessed recently, so if your website is the most accessed content on IPFS you can host it for free just by sharing it once and users will have relatively quick access to it because nodes directly connected to them will probably have a cached copy already. If requests are rare, expect to host it yourself or pay a pinning service, and expect higher latency as users will be requesting content hosted multiple hops away. You should care whether the tech is butterflies or turtles, because you can't compare butterflies and turtles -- or you can, but the comparison breaks down when you ask which will get to an undefined point x quicker. If x is in the air, butterflies; if x is in the water, turtles.
- icebraining 7y ago
- neiman 7y agoGreat job, simple and easy, as a tool should be. I'm definitely gonna use it.
- agentofuser 7y agoThank you! It makes me very happy to hear that. Feel free to ping me if you run into any trouble (even if it's just a non-showstopper like some unnecessary friction or papercut.) Also keen on hearing what services I should add next. I don't use AWS Route 53 but I think it would be a good option to support for instance.
- neiman 7y agoWe're working on a small browser extension for static ipfs websites where this comes in handy. I'll ping to let you know how it goes.
- dane-pgp 7y agoDoes it make sense to add support for Signed HTTP Exchanges (SXG) to this? https://github.com/ipfs/in-web-browsers/issues/121 https://github.com/ipfs/in-web-browsers/issues/121
- agentofuser 7y agoGood idea! I've been following Web Packaging from a distance, so would need to do some research, but from the looks of it, ipfs-deploy could automate packaging up a directory into an SXG before uploading it to pinners. Gotta figure out how to the signing part though. I'll look into it!
- deleted 7y ago[deleted]