Skip to content

This is My Second IPFS Post

Dumped everything and started over with mkdocs + mkdocs-material.

You can reach this site a few different ways via ipfs

All three use ipns and the first two use it via cloudflare. The last one via ipfs.io / dweb.link.

No pinning services are paid for so you get what you get. :|

Web3

To make everything faster I'm using github pages and I'm also using cloudflare pages. This means that the content should be accessible via web2 and web3. Which I think is pretty damn neat! So whenever I push a commit to github everything rebuilds and deploys. Even my selfhosted ipfs pinning services!

IPFS Pinning

As mentioned above, have selfhosted pinning. That's just a fancy way of saying I'm running ipfs and have a set of cron jobs to blast my stuff out to the network.

@weekly ipfs bitswap reprovide  
@monthly ipfs repo gc >/dev/null 2>&1  
@hourly ipfs pin add -r /ipns/k51qzi5uqu5djjziu1k5ty1a4xo13pn4bs4at2hk0u6f9bdllv5k47bqvv0yz9 >/dev/null 2>&1  
@hourly ipfs refs /ipns/w4ugh.radio | awk {print $1}' | while IFS= read -r line; do ipfs pin add -r ${line}; done  
@monthly ipfs ls /ipns/w4ugh.radio | awk '{print $1}' | while IFS= read -r line; do ipfs dht provide -r ${line}; done >/dev/null 2>&1

I have ZERO ideas if this is the right or best way to do this. I could be COMPLETELY wrong so don't rely on this as the right way to do this. I'm sure someone who knows a lot more than I can open an issue or PR on this post with the correct way to do any of that.

So YMMV and enjoy!