Articles
Longer pieces on how something works and why I set it up the way I did.
-
Collection Sets and Category Collections
One boolean in the frontmatter told the photo sets of my old site apart from pure navigation nodes, so only finished sets reached the archive.
-
Adding Notes, Links and Archives
Three sections of my old Astro site: short notes rendered inline, a link log as a data collection, and one archive across every content type.
-
Photo Albums with Astro's Content Layer
Album pages on top of the photo stream of my old site: a content collection per album, covers by filename, album-scoped photo routes and a sub-nav.
-
Building the Photo Stream
The photo stream of my old Astro site: JSON sidecars next to each JPG, import.meta.glob, a justified grid and batches revealed on scroll.
-
Photo Sidecars with a Vision Model
The script vision.ts of my old site: EXIF data and a vision model's alt text, titles and tags in a JSON file next to each photo, generated locally before the deploy.
-
Obsidian to VPS Pipeline: Sync, Pull and Redeploy
One shell script on the Mac that pulls the site repository on the VPS, rsyncs the posts from the Obsidian vault and rebuilds the Astro container.
-
Triggering VPS Deploys with GitHub Actions
A GitHub Actions workflow that opens an SSH session to the VPS on every push to main and lets the server pull and rebuild itself.
-
Mirroring GitHub to Codeberg
A GitHub Actions workflow that mirrors branches and tags to Codeberg with plain git push over SSH, without a third-party action.
-
Updating the Website Repository on a VPS
A repeatable update flow on the VPS: check the working tree, pull with --ff-only, rebuild with podman-compose, verify, roll back, all in one script.