Publish IPFS webapps which require user consent to update, see:
This repo contains a sort of web bootloader, you will style this repo as you like and then you will publish this repo and your app to IPFS. Your app is a fork of IPFS-boot-react or IPFS-boot-choo. You will host a file versions.json on any http server and inside this file an array of items describe versions of your app which users choose from.
It is intended that you share the source of your fork of IPFS-boot and IPFS-boot-react or IPFS-boot-choo. The sources allow users to build and see the IPFS CID (a hash) you publish is the same as what they get from source. The CID of IPFS-boot will be the URL of your app, the CID of each version of your app goes in versions.json, and the bootloader polls this file.
The bootloader only gets published once but your app updates can include CSS which styles the bootloader. This all actually works, and it works offline(!), give it a try.
The aim is reproducible builds so docker is involved
docker buildx build --platform=linux/amd64 -t ipfs-boot .
docker run --rm -i --platform=linux/amd64 -v ./dist:/root/dist ipfs-boot
Read the guide on choosing an IPFS pin service then
cp example.env .env
docker buildx build --platform=linux/amd64 -f Dockerfile.pin -t ipfs-pin .
docker run --rm -i --platform=linux/amd64 -v ./dist:/root/dist --env-file .env ipfs-pin
> CIDv0 = QmQcFZUsp47bckyJTwzL6mr4HWNrGvdnRW6Z95jJbxC5bF
> CIDv1 = bafybeibbwz7bew6l3e5lsgneebvhfe63qclvhygkmh6ba7nk566a4qdy7i
> upload: ../dist.car to s3://bucket-name/bafybeibbwz7bew6l3e5lsgneebvhfe63qclvhygkmh6ba7nk566a4qdy7i
> done: https://bafybeibbwz7bew6l3e5lsgneebvhfe63qclvhygkmh6ba7nk566a4qdy7i.ipfs.dweb.link
Your bootloader is now live and discoverable with v0 and v1 CIDs, see gateways
http://localhost:8080 for quicker iterations on the bootloader
npm --prefix javascript/ install
npm --prefix javascript/ run dev
You may be wondering about the rust/ dir or dist/nitro_wasm.wasm. The Rust allows IPFS-boot to support attestation with AWS Nitro servers, so reproducible clients and servers, see: lock.host
Two files nitro_wasm.js and nitro_wasm.wasm are checked into source within javascript/assets/, these are tested by github actions, to build from source do:
docker buildx build --platform=linux/amd64 -f Dockerfile.wasm -t ipfs-wasm .
docker run --rm -i --platform=linux/amd64 -v ./dist:/root/dist ipfs-wasm
sha256sum javascript/assets/nitro_wasm.wasm
sha256sum dist/nitro_wasm.wasm
Please if you want to style the bootloader, open a PR ^.^
If you clicked "boot!" without reading: you can return to boot list anytime by add #boot to the url
- react https://bafybeifehbm2um54qvfifprtbkgbt25ndkq6k26zjlbe33t2j62gdjwn2m.ipfs.dweb.link
- choo https://bafybeibbwz7bew6l3e5lsgneebvhfe63qclvhygkmh6ba7nk566a4qdy7i.ipfs.dweb.link
MIT