Make plan for FOC decentralized hosting #2
Description
Done Criteria
We have a runbook that lists:
- which of our web-properties we want to ensure has a decentralized backup (i.e., Filecon Pinned, ENS contenthash set)
- what ENS domains they each map to
- who has credentials to update the corresponding ENS domain contenthash fields
Why Important
We want to ensure key functionality of our decentralized toolchain is still accessible, even if platforms like Cloudflare are down. It is a selling point of our tech, and it's otherwise a bad look if it doesn't work when AWS/Cloudflare are down.
Notes
- This doesn't need to be automated. It's fine for us to be reactive and just update ENS domain contenthashes manually (even reactively). We just need to have all the steps to do that.
Note that there are even complications with automating this:- Gas costs for ENS domain updates
- ENS domain ownership should be under a multisig but that would get int he way of contenthash updates in CI
- Any site that we do want with decentrlaized hosting needs to be pinning (presumably with the filecoin pin GitHub action so that we have IPFS CID to set the ENS domain contenthashh to)