We've had our eye on Agent of User's great ipfs-deploy tool for a while now. It is a quick way to get a static website served up through a regular Web2 domain name. It automates both IPFS uploading / pinning as well as updating DNS.
Upload static website to IPFS pinning services and optionally update DNS.
The goal of
ipfs-deploy is to make it as easy as possible to
deploy a static website to IPFS.
Table of Contents
npm install -g ipfs-deploy
yarn global add ipfs-deploy
You can call it either as
ipd or as
ipd public/ ipfs-deploy public/
You can run it directly with npx without needing to install anything:
npx ipfs-deploy _site
It will deploy to a public pinning service and give you a link to
ipfs.io/ipfs/your-hash so you can check it out.
You can get started just by typing out
ipd and it will have smart defaults
By default, it deploys to Infura, which doesn't need signup and you'll get…
"Adding support prompted us to add another feature to our web api: manipulation of InterPlanetary Linked Data (IPLD) nodes." – Daniel Holmgren
Right now we're using this ourselves for some website experiments, leaning on the Cloudflare integration in ipfs-deploy to automate DNS updates. DNS Automation is something that we're building into the Fission Suite directly, as part of our "batteries included" approach.
As well, ipfs-deploy specifically works without a local IPFS node. The direction we're going with the Fission tools is going to assume that we can run a local IPFS node everywhere that our CLI can be installed, so we'll be leaning into "native" IPFS protocol functionality. We'll be release an alpha of our Fission CLI shortly so you can check out our approach.
Read Agent of User's Complete Beginner's Guide to Deploying Your First Static Website to IPFS for the full run down on using ipfs-deploy.
Skipping to the end, you can use your Fission credentials & Cloudflare API keys to run this one liner:
ipd -p fission -d cloudflare