I Moved My Website to IPFS

April 4th 2021

Until now my go-to cloud provider for static webapps were Netlify or Render (which internally deploys on AWS, GCP, etc) as it addressed my requirement from a infra/deployment toolchain element perfectly.

Since the advent of blockchain solutions and interest and efforts towards Web3.0, it was only a matter of time before we would have solutions for deploying professional webapps on a distributed network. And that time is here! This is a notable event in the life of Web3.0, particularly as it enables many of us to migrate our existing projects from traditional centralized organizations (e.g AWS, GCP, Azure, etc) over to a distributed network!

What is IPFS

IPFS is a distributed system for storing and accessing files, websites, applications, and data. [1]

It is a protocol and peer-to-peer network for storing and sharing data in a distributed file system. IPFS uses content-addressing to uniquely identify each file in a global namespace connecting all computing devices.[2]

Why I moved my website to IPFS

Whether we accept it or not (whether we like it or not) we are already in early stages of Web3.0 and it's only a matter of time before the principles of Web3.0 become widely adopted and even required.

Distributed computing and storage has always been fascinating to me. Just the thought that we could leverage millions of personal computers sitting idle at home around the world, potentially even rewarding those computers (nodes) for choosing to be pillars and building blocks in the Web3.0 network. Amazing! It's the way it should be! (:bows)

This blog, used to be deployed on Netlify, and since the time IPFS started to get more advanced and stable, I was waiting to migrate my website over and test it out, and see how different (if at all) the experience would be.

And very importantly I choose to be part of the generation that takes Web3.0 into production environments and in mission critical systems.

Couple of weeks ago, I made the decision to move this website onto IPFS (and consequently Filcoin). I started playing around with the CLI and looking for ways to go about it. And quickly enough I came across is a service which handles deployment of webapps on the IPFS network. It takes care of pinning content, versioning, custom domain management and other deployment related functionalities.

How to setup a site/webapp

If you are familiar with Netlify, Heroku, Render, then is no different! currently allows you to connect Github repos (Gitlab and Bitbucket are coming soon …), set the branch, build command and the directory to be published on to IPFS. And that's it! As simple as that.

Below is my configuration for this website

Fleek Configuration

Did I have any issues?

Maybe just a couple :) When I pushed to my git repo, the deploy got stuck a couple of times. I tried updating the site-name in the site configuration and domain showed a 404. But, these were easy to fix, by just redeploying and re-verifying my domain. And the live chat customer service replied pretty much immediately to explain the situation and to let me know that everything is just fine!

However, these minor issues are expected at such an early stage of the service. But very importantly, it works much better than I expected it to! I am extremely happy with Fleek (and IPFS) and I don't plan to move away anytime soon!

Distributed Computing?

While IPFS and Fleek work perfectly for distributed storage, and therefore can be a viable option for deploying small to large scale Javascript webapps; what about deploying a micro-service (e.g a rest API service)? The answer could be Holochain.

If you read the about me page you see that I am very bullish on Holochain.

All-in-all I am thrilled with all the innovation in this space and we can expect amazing and ground breaking products and services to come out in the very near future.