7/30/25
The content of this blog is contained in a SQLite database (built using BigBlog of course) but databases aren't immutable. So what gives?
If you copy that database into the container at build time then the resulting image renders it immutable. This was done for a very simple reason ... it's easy.
You get the idea. This blog runs from an ASP.NET Core application. The application and the database are embedded in the image and therefore immutable.
What about when the blog content changes?
My blog content is written in markdown. My markdown editor of choice is Typora. I don't need an online editor or blogging system. I don't want an online database.
This blog is simple. I just write, commit, and build.
All the blog content exists in the repository right alongside the application source code. If anything changes then I can easily build another image with the latest bits. Deploying the application deploys the latest blog content.
The only downside that I can think of is what would happen if I needed to publish a blog post without the latest application code. This is the second post and this site is actively being developed. I have not run into this problem and I really don't intend to. There are ways to mitigate the changes using branches and/or tags. I have options.
For now, let's keep easy. This blog is immutable.