Deployment Guide: GitHub Pages → Cloudflare Workers

Overview

This site is configured to deploy to Cloudflare Workers with static assets, replacing the previous GitHub Pages setup.

Prerequisites

1. Domain atxconsulting.com must be added to Cloudflare (already done)
2. GitHub secrets configured:
   • CLOUDFLARE_API_TOKEN - API token with Workers Scripts:Edit and Workers Routes:Edit permissions
   • CLOUDFLARE_ACCOUNT_ID - Your Cloudflare account ID

Setup Steps

1. Configure Cloudflare DNS & Routes

Run the audit tool to inspect current setup:

CLOUDFLARE_API_TOKEN=... CLOUDFLARE_ACCOUNT_ID=... uv run configure-cloudflare audit

Apply the configuration (creates/updates DNS and Worker routes):

CLOUDFLARE_API_TOKEN=... uv run configure-cloudflare apply

2. Deploy the Worker

Push to master branch or trigger workflow manually:

git push origin master

Or deploy locally:

npm ci
npm run build
npx wrangler deploy

3. Verify Deployment

• Check GitHub Actions: https://github.com/tjfontaine/tjfontaine.github.io/actions
• Visit: https://atxconsulting.com
• Check logs: npx wrangler tail or view in Cloudflare dashboard

Key Files

• wrangler.toml - Worker configuration
• worker/index.js - Worker script (serves static assets)
• .github/workflows/deploy.yml - CI/CD pipeline
• scripts/configure_cloudflare.py - DNS/route setup tool

Features

• Observability: Full request logging enabled (100% sampling)
• Caching: Automatic edge caching via Workers Static Assets
• Auto-trailing-slash: HTML handling configured for clean URLs
• Global CDN: Served from 300+ Cloudflare locations worldwide

Troubleshooting

• DNS not resolving: Ensure zone is active in Cloudflare and nameservers are updated
• 404 errors: Check that npm run build generates _site/ directory
• Worker errors: Run npx wrangler tail to see real-time logs
• GitHub Actions failing: Verify secrets are set correctly in repo settings

Rolling Back

To roll back to a previous deployment:

npx wrangler rollback

Or redeploy a specific version from the Cloudflare dashboard.