Moved to Cloudflare Pages

When this blog, originally hosted on a .dev domain, first came into existence, it found its home in a Google Cloud Platform (GCP) Bucket. The setup was straightforward:

  • Public LB
  • Bucket as backend

Deployment process was equally simple, thanks to Github actions. However, simplicity came at a cost—about $12 USD per month. While not exorbitant, it’s equivalent to a regular visit to Starbucks. In today’s world, there are more cost-effective alternatives that can fulfill the same purpose: hosting a static webpage with automated deployments straight from GitHub. Enter “GitOps.”

Cloudflare Pages

I’ve been a longtime user of Cloudflare’s services. In fact, for one of my side project, I’m actively using Cloudflare Tunnels. Therefore, switching to Cloudflare Pages seemed the naturla choice.

How does it work?

The process is refreshingly straightforward. You can do either:

  1. Git integration: You can easily configure a git integration, but it requires access to your Cloudflare account. This approach offers seamless synchronization with your repository.
  2. Pages-action: With this approach, whenever you open a pull request, you’ll receive a new URL showcasing a preview of your build. Once merged into your main branch, it becomes publicly accessible.

Then, whenever you open a pull-request, you’ll get a new URL with the preview of your build. Once mereged into your main branch, it will be publicly available:

How much does it cost?

Migrating to Cloudflare Pages not only simplifies the deployment process but also offers cost savings, making it a win-win choice for hosting static web pages with automatic deployments.

It starts from $0 USD/mo.