Configure and manage the GitLab container registry, including storage backends, garbage collection, and authentication.
Configure and manage the GitLab container registry, including storage backends, garbage collection, and authentication.
My personal website
Distribution implementation for storing and distributing of container images and artifacts
------- Context ------- S3 is fast and cheap.
GitHub, Github Actions, and the GitHub Container Registry have been how I've been handling builds, but it's been slow, and it's started to seem absurd to have all these builds occurring in some random datacenter presumably on the other side of the Atlantic ocean, that I am then pulling back to a server in Europe. I started fishing around for a locally hosted replacement, coming across Forgejo, Woodpecker CI, and OneDev in addition to more familiar names like GitLab and SourceHut. At some point it occurred to me that this was a lot of ceremony for something relatively simple. How hard could it be just to have a git remote and hang some builds off it? I'm not trying to launch my own GitHub here.
Running harbor for internal images and as a proxy for external registries
My side project Abot for Slack, has been around for ~7 years, i.e., since Rails 5.1. It's now yielding passive income while running on an almost complete autopilot. But I'm still keeping its dependencies up-to-date. The recent migration to Rails 8 was arguably the most impactful in the app's lifetime. In this blog post, I'll describe features introduced in the newest version of the framework and how they affected my project.