Migrating My Blog

2-minute read
astromigrationself-hostingwaline

Background

I built this blog using a heavy stack — don’t laugh — with Laravel, Filament, MySQL, and Redis for caching. Also, I deployed this via containers, so I was forced to manage the backup of my databases using volumes. This was working fine, but I needed more.

Anakin: “I want more… and I know I shouldn’t”

I needed my blog to support Markdown, since I write everything in Obsidian, and also sensible defaults for common features like RSS, asset optimization, and support for web analytics (Umami) and a comment section. Other reasons are that I felt bored with this blog, so trying different things was playing a role in this migration.

Therefore, I spent a little bit of time searching for alternatives. I found that I could use Astro, Hugo, or Ghost; all these tools are great and can give me the things that I’m searching for. However, comparing the pros and cons of these tools, I decided to use Astro because it’s widely used by people, and has great support for Markdown files and, by default, for RSS.

As a result, no more database — a small database won’t be harmful — no cert renewal, no queue workers, and writing a post is now just committing a Markdown file from Obsidian.

Furthermore, adding a comment section to each post will make the post live and the whole blog alive. For this I use a safe comment system, Waline. I know I said no databases, but this is only a small one; therefore, I used the most deployed database, SQLite.

In addition, I added categories, to categorize the posts, and also a search, to search instead of going from page to page. Since in my day-to-day I come across some really nice blogs and news, and I can’t make a post about them just to give a thought, I use this concept of macros to post thoughts on news and other things.

Summary

I went from using Laravel, Filament, MySQL, Redis, Supervisor, Certbot, and backup/restore containers to a simple stack: a static Astro site, the Markdown in git and the RSS, and a single Waline container for comments, both auto-deploying via GitHub.