Recently, Cloudflare kept nudging me to migrate from Pages to Workers - and by “nudging,” I mean waving a persistent banner in my face like a toddler with a glitter-filled craft project. I’ve deployed a few sites to Pages and appreciated the simple setup, but after digging into Workers, I decided to give it a go. Let’s walk through the pros, the cons, and how I’ve reworked my CI/CD pipeline. As a cherry on top, I’ll show you how I wired up Slack to keep me posted on every build and deploy - because sometimes I like someone to notice my accomplishments.

I’ve used Cloudflare for what feels like ages - first for accessing my home lab (which at the time was a Raspberry Pi updating the ip address with DDNS), later at work to protect applications. Today, I use it for domains, DNS, tunnels, security, and more. It’s a very versatile tool for both hobby and business.

This is the first time I’ve used Cloudflare Pages. I thought about self-hosting a static site, and just using my Caddy reverse proxy or Nginx to serve up the static site. However, I thought I’d give Cloudflare Pages a shot because