<![CDATA[New blog post: Speeding Up Forgejo CI with a Custom OCI Image]]>New blog post: Speeding Up Forgejo CI with a Custom OCI Image

My blog's pipeline spent more time installing dependencies than actually building the site. Two commits and one Containerfile later, that step is gone entirely.

Bonus: Forgejo ships with a built-in OCI container registry, so the whole thing is self-contained on a single instance. No Docker Hub, no external registry.

Link Preview Image
Speeding Up Forgejo CI with a Custom OCI Image

How I cut my blog’s CI/CD build time in half by baking dependencies into a custom container image and hosting it in Forgejo’s built-in OCI registry.

favicon

Larvitz Blog (blog.hofstede.it)

]]>https://board.circlewithadot.net/topic/4925ed86-5bd6-4674-97e5-210a8bc6eb2a/new-blog-post-speeding-up-forgejo-ci-with-a-custom-oci-imageRSS for NodeMon, 06 Apr 2026 06:37:01 GMTWed, 01 Apr 2026 12:50:38 GMT60<![CDATA[Reply to New blog post: Speeding Up Forgejo CI with a Custom OCI Image on Wed, 01 Apr 2026 14:05:18 GMT]]>@kevin The article with that is linked in the article 🙂

Link Preview Image
Hosting a Static Blog on FreeBSD with Bastille Jails and Automated Deployment

A full-stack overview of hosting a Pelican blog on FreeBSD 15.0 using Bastille jails, Caddy reverse proxy, and automated CI/CD deployment via Forgejo Actions.

favicon

Larvitz Blog (blog.hofstede.it)

I use rrsync (restricted rsync) on FreeBSD for that.

]]>https://board.circlewithadot.net/post/https://burningboard.net/users/Larvitz/statuses/116329828766511495https://board.circlewithadot.net/post/https://burningboard.net/users/Larvitz/statuses/116329828766511495Wed, 01 Apr 2026 14:05:18 GMT