Show HN: IPFS-Deploy – Zero-Config CLI to Deploy Static Websites to IPFS

https://github.com/agentofuser/ipfs-deploy

by agentofuser • 7 years ago

150 34 7 years ago

agentofuser10• 7 years ago

Hi! 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• 7 years ago

Is 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.

icebraining3• 7 years ago

Not 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.

bravura• 7 years ago

With IPFS what are the costs to keep your site live?

theamk• 7 years ago

It 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)

gitgud2• 7 years ago

How does that compare with AWS? Is IPFS worth using for a CDN? (apologies for the acronyms...)

agentofuser10• 7 years ago

Yep. That is the price practiced by Pinata[1] after 1GB, and by Eternum[2] at the outset (no free tier).

[1] https://pinata.cloud/ [2]: https://www.eternum.io/

neiman4• 7 years ago

Afaik. in the pinning method this tool uses, it costs nothing. But you can't be sure that it will really be always live (it depends on the good heart of the pinning service you used).

If you want to really ensure it's live you should run at least one node that pins it yourself (or pay someone to do that)

agentofuser10• 7 years ago

Yeah both Infura and Pinata are free for up to 1Gb or something like that, which is fine for most static websites and blogs. But those are startups, so I agree that for long-term permanence it's better to do some self-hosting down the line.

neiman4• 7 years ago

Great job, simple and easy, as a tool should be. I'm definitely gonna use it.

agentofuser10• 7 years ago

Thank 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.

neiman4• 7 years ago

We'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• 7 years ago

Does it make sense to add support for Signed HTTP Exchanges (SXG) to this?

https://github.com/ipfs/in-web-browsers/issues/121

agentofuser10• 7 years ago

Good 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!

Show HN: IPFS-Deploy – Zero-Config CLI to Deploy Static Websites to IPFS

Related Stories