Handling updates of IPFS-based web pages

I’ve seen how easy it is to deploy and pin a “single-page” website using IPFS, but the part I am not understanding: what happens when you want to update the content? Do you just 1) unpin the old, and 2) redeploy the page again? Presuming you had some domain service, do you have to update to the new hash ID (CID?)? Is there a better way? Thanks!

1 Like

Did you check ipns?

Yes, that looks like a promising way to go. I think what could be done is 1) use IPNS to create a “static” CID for your project, and then 2) use DNS or some other same service as an alias to make it easier to find. Does it sound like I’m on the right track? Thank you!

I’m not familiar with setting a DNS for ipfs but I saw a webpage doing it the other day:

It uses CloudFlare.

❯ nslookup fdroid.evanito.com
Server:         1.1.1.1
Address:        1.1.1.1#53

Non-authoritative answer:
fdroid.evanito.com      canonical name = cloudflare-ipfs.com.
Name:   cloudflare-ipfs.com
Address: 104.17.64.14
Name:   cloudflare-ipfs.com
Address: 104.17.96.13
Name:   cloudflare-ipfs.com
Address: 2606:4700::6811:400e
Name:   cloudflare-ipfs.com
Address: 2606:4700::6811:600d

There’s seem to be other ways to do DNS. This repo mentions dnslink:

1 Like

Oh yeah, that was the one I was going to do… dnslink. Thanks for the link, and let you know how it goes.

I believe you’ll find these resources quite helpful:

Good luck / I hope you figured it out :slight_smile:.

Edit: Btw ipfs-sync was originally designed specifically for keeping websites updated.