From one command to a URL that loads.
Deployment guides for open-source projects. Every guide is run on a blank server, in order, with the version numbers pinned and the failures left in.
Ctrl K
3 guidesupdated
How these guides are made.
Every guide starts on a blank machine: a fresh VPS, an empty repo, nothing pre-installed. I run the steps in order, pin the version numbers, and leave the dead ends in. If a command fails on a clean install, it fails here too, with the fix sitting right next to it.
- Blank machine to live URLNo skipped steps, no "it should just work".
- Versions pinned, dates stampedEach guide names the exact release it was tested against.
- Failures kept inError messages stay, because you will hit them too.
Drop a 4:5 portrait at
public/assets/portrait.jpgLatest guides
A new walkthrough every week or two.
Hello world: why this blog runs on Astro2 minEvery few years I rebuild this site. Not because the old one broke, but because the act of rebuilding is a good excuse to question assumptions. This…
Deploying Astro to Cloudflare Pages without surprises2 minAstro outputs a plain dist/ folder, which is exactly what Cloudflare Pages wants. In theory the whole deployment is three fields. In practice there…
Content collections: the feature that keeps a blog honest1 minHere's a failure mode I've hit more than once: you write a post, it renders fine, and it never shows up in the list. The cause is one missing…