IPFS Deployment option

[kallisti5]

hugo supports multiple deployers via hugo deploy

ipfs should be added to the deployment options. With the following arguments:

• ipfs api server url
• ipns public key (optional)

Hugo could self-publish websites to an IPFS node. This would make the site content available through any public IPFS gateway node.

For those without IPFS knowledge, I made a "crash course" infographic here: https://cloudflare-ipfs.com/ipfs/Qmbq5hoM4eCeCnSSTcXSyaYNjNHgCmeQ58VuqJxU1tu3ho/IPFS_For_Sysadmins.pdf

IPFS is attractive because it's literally "make your own cloud"

I published a "R1B2" release page for Haiku here as an example:

• http://ipfs.haiku-os.org A 209.94.90.1 (ip for ipfs.io gateway)
• ipfs.haiku-os.org. 3600 IN TXT "dnslink=/ipfs/QmXtYCCM8Kt7Q9DbXYKHy8bUQve9zauNiKUZs57bnphBtw"

Essentially:

• ipfs.haiku-os.org goes to ipfs.io (but it can go to any ipfs gateway)
• ipfs.io checks for /ipns/ipfs.haiku-os.org, and looks at that TXT record
• ipfs.io renders the site at /ipfs/QmXtYCCM8Kt7Q9DbXYKHy8bUQve9zauNiKUZs57bnphBtw

I made another example with https://terarocket.io this site uses the free Cloudflare IPFS gateway and has HTTPS

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help. If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open. If this is a feature request, and you feel that it is still relevant and valuable, please tell us why. This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

[vanbroup]

I think this should stay on the backlog.