OK that took the whole morning, mostly getting the ingress controller to correctly serve #tls (I didn't realise that in addition to setting the host names and cert secret, I also needed to ensure that each named server has an explicit rules block otherwise nginx uses the catch-all rules and doesn't apply TLS).
So now, when I push my #gnustepweb app to main, #woodpeckerCI builds and pushes to #quayio and #argoCD pulls and deploys the app in my prod cluster.
We want to know if we have windows user and if it would be worth having our released binarys signed.
Unhappy with #GitHub or its owner #Microsoft?
Check out @Codeberg. It works, migration is easy for basic repos and it uses #FOSS #CI (#WoodpeckerCI) which you can also host yourself which helps break dependence on those burning the planet for profit, and gives *you* control.
It's an EU based non-profit run by enthusiasts like us for us.
It's free, or if you like to be able to vote on decisions, membership costs about 60 Euros/year.
It also helps you feel better, or maybe that's just me ๐
Introducing Chilly Willy Agent!
It provisions a private Woodpecker CI agent on Hetzner Cloud:
- IPv6-only by default (NAT66, optional DNS64 for IPv4-only upstreams)
- Fedora CoreOS + Podman runtime
- ./chilly-willy-agent wrapper plus make targets, all hitting the Hetzner Cloud API via curl
- Image-pin enforcement, optional firewall, multi-agent
Built primarily for Codeberg CI. Apache 2.0 licensed.
https://codeberg.org/head1328/chilly-willy-agent
#OpenSource #Codeberg #WoodpeckerCI #FedoraCoreOS #Podman #SelfHosting
New blog post: https://blog.mei-home.net/posts/smokeweb-db-ci/
This one has a bit of Golang programming (still not sure about programming posts - I don't think I'm particularly good at writing them) and some CI setup for database testing of a Golang app in Woodpecker CI.
Special thanks go to @louis for preventing me from going on a sidequest switching my entire CI system.
The next #release (3.14.0) takes it's time ... now we are confident and made our final #rc (https://github.com/woodpecker-ci/woodpecker/releases/tag/v3.14.0-rc.2)
please test it, so we can catch regressions if any exist ;)
RE: https://social.treehouse.systems/@whitequark/116454915873481567
Anyone publishing a Quarto blog with Codeberg Pages? I'm new to this automation stuff, and can't decide between WebHooks, Forgejo Actions, and WoodPecker CI. If I use actions or WoodPecker, it would be just for "quarto render"; any R code output is frozen and will be run on my own computer. I have a custom domain.
#QuartoPub #CodebergPages #GitPages #ForgejoActions #WoodPeckerCI
Finally done. I can now run database tests for my Go app in Woodpecker with a real Postgres DB. So finally back to coding now.
Also: I think it is rather beneficial for my career as a CI engineer that nobody can see my Makefile and CI setup.