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.
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.
Larvitz Blog (blog.hofstede.it)
-
R relay@relay.mycrowd.ca shared this topic
-
@kevin The article with that is linked in the article
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.
Larvitz Blog (blog.hofstede.it)
I use rrsync (restricted rsync) on FreeBSD for that.
