Path A: Cloudflare Pages
This is a member-only chapter. Log in with your Signal Over Noise membership email to continue.
Log in to readModule 5 · Section 2 of 5
Path A: Cloudflare Pages
Cloudflare Pages is free for most use cases, globally distributed, and has zero configuration for SSL. It connects directly to a Git repository and deploys on push. For content sites with no server-side logic, it’s the right choice.
What it’s right for: Anything fully static. A personal site, blog, portfolio, documentation, landing page. Anything that doesn’t need Edge Functions or specific server behaviour.
What I deploy here: sketchscript.app and definitelyrealproducts.com both run on Cloudflare Pages.
Setup
- Push your site to a GitHub repository.
- Log into the Cloudflare dashboard and go to Workers & Pages > Create > Pages.
- Connect your GitHub account and select the repository.
- Set the build settings:
- Framework preset: Astro
- Build command:
npm run build - Build output directory:
dist
- Deploy.
That’s it. Cloudflare gives you a *.pages.dev subdomain immediately. You can add a custom domain in the Pages settings once the deploy succeeds.
Custom Domain
In Cloudflare Pages > Custom Domains, add your domain. If your DNS is already on Cloudflare (recommended), the DNS record is created automatically. If your DNS is elsewhere, you’ll add a CNAME pointing to your *.pages.dev subdomain.
SSL is automatic. There’s nothing to configure.
Environment Variables
If your Astro site uses environment variables at build time, add them in Pages > Settings > Environment Variables. Prefix anything you want available in client-side code with PUBLIC_.