I set up Renovate to scan docker-compose files on its own, open PRs in Forgejo with new image versions, and let Komodo redeploy the stack automatically after merge.

Why self-hosted GitHub Actions on a single repository (article 3) turned out not to be the choice worth keeping - and how I reverted back to the proven two-repository Forgejo setup, walking through an honest comparison of both options along the way.

How I moved the build and deploy of ProHomelab from a homemade Forgejo runner to a self-hosted GitHub Actions runner on my own LXC, merged content and site into a single repository - and what didn’t go according to plan.

Fully automating ProHomeLab publishing: I write an article in Obsidian, the changes automatically land in Forgejo, Forgejo Actions triggers a Hugo build on a Blowfish LXC, and the finished site gets uploaded with no manual steps at all.