I wanted a home on the web that was not a timeline on someone else's platform: a slow place of my own for blog posts, notes, links and photos. That place was adrian-altner.de, built with Astro. The source lived in my own Git repository at git.altner.cloud/adrian/adrian-altner.de.1
The first post
The site went live on 1 December 2025 with a short post called "Hello, World!". It explained the phrase: one of the first lines a new programming student writes, a way of saying hello in the world of coding.2
How it was built
- Astro on the Node.js standalone adapter, TypeScript throughout.
- Rendering: most routes were prerendered as static pages. A handful of pages used server-side rendering where they needed it.
- Content: Astro content collections with Zod schemas, so the frontmatter was type-checked at build time. A typo in a
pubDatefailed the build instead of producing a broken page. - IndieWeb: posts were syndicated to Mastodon by my own POSSE script. Incoming webmentions came from webmention.io at build time and appeared on the post they referred to. Microformats2 markup ran through the whole site for anyone parsing the HTML.
- Photos: JPG files with JSON sidecars, organised into nested collections with breadcrumb navigation. No database and no image CDN, only files on disk. The sidecars came from a script described in Photo Sidecars with a Vision Model.
- Feeds: an RSS feed for every content type.1
How it ran
The site ran as a container with Podman on a Debian VPS, with Caddy in front. The guides from that time:
- Astro SSR with Podman: From Local Setup to VPS, the local container setup.
- Deploying Astro SSR to a VPS with Podman and Caddy as Reverse Proxy with HTTPS and a Canonical Host.
- Updating the Website Repository on a VPS, Operating Astro SSR in Production with Podman and Triggering VPS Deploys with GitHub Actions.
- Obsidian to VPS Pipeline for publishing posts from my Obsidian vault, and Obsidian Wiki-Links in Astro with a Remark Plugin for the links inside them.
- Topic
-
- Static Website A website made of finished HTML files that are built once and then served unchanged. No server code, no database.
- Uses
-
- Astro Tool for building websites from content such as Markdown. Ships plain HTML by default and only loads JavaScript where it is needed.
- Caddy Web server and reverse proxy that obtains and renews TLS certificates on its own, configured in a short Caddyfile.
- Podman Container engine without a background daemon that runs rootless by default on Linux and uses the same commands on macOS and on a server.
- Mentioned
-
- Astro SSR with Podman: From Local Setup to VPS Astro with the Node standalone adapter in a two-stage Podman container, run locally with the same compose file that later goes to the VPS.
- Caddy as Reverse Proxy with HTTPS and a Canonical Host Caddy in front of a container on a VPS: automatic TLS from Let's Encrypt, www redirected to the bare domain, the app port closed to the outside.
- Deploying Astro SSR to a VPS with Podman Moving the Astro SSR container to a fresh Debian VPS: Podman from the distro packages, a read-only deploy key and the same compose file.
- 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.
- Obsidian Wiki-Links in Astro with a Remark Plugin A small Remark plugin that turns Obsidian [[wiki-links]] into normal links at build time, with labels, heading anchors and a fallback for unknown targets.
- Operating Astro SSR in Production with Podman A short runbook for the Astro container on the VPS: start and stop, health checks, the four-command update, rollback by commit and Caddy checks.
- 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.
- 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.
- 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.
- Tags