Hacker News Reader

Comment by unsnap_biceps | Hacker News Reader

I don't really need the web interface, but the actions are useful. Automatically building updated docker images and software packages is enough to accept the gitea complications, but gitlab is way too heavy IMHO

View on HN

You can do that via hooks. You could probably even manage to hook up a CI engine like woodpecker via hooks and do it entirely that way.

Gitea or Forgejo with actions is almost certainly easier, but it's possible to do it with pure git.

Actions support running on times. Sure, I could wire up a Rube Goldberg of systemd user timers and user units that trigger on hooks or I can store some yaml in the repo and it just works (tm)(r).

Sometimes the juice isn't worth the squeeze, and for me, doing it all custom isn't worth it for my home projects.

What's wrong with a server-side post-receive hook?

there's nothing wrong with it, just more work then I'd like. I'd have to setup a CI system or build my own to handle the dependency management of the jobs and, as I said, time based job runs (Rebuild this image monthly regardless of any code changes) add enough complexity that using the gitea container for the actions and ci is worth it compared to something marginally lighter weight.

That's an interesting perspective.

I feel like this is one of those topics where compromise is futile. I use GitLab at work and use plain git on personal projects. I don't like spending time on tools that aren't either teaching me or paying me.

Reply on news.ycombinator.com