@jwildeboer It's like as we the FLOSS community insisted to not play on BigTec's playground anymore, but continue playing the very same game in our backyards. 🙃
Notices by pluhmen (pluhmen@kanoa.de)
-
Embed this notice
pluhmen (pluhmen@kanoa.de)'s status on Tuesday, 04-Mar-2025 04:49:40 JST pluhmen
-
Embed this notice
pluhmen (pluhmen@kanoa.de)'s status on Tuesday, 04-Mar-2025 04:49:38 JST pluhmen
@jwildeboer In general I agree, but propagating TypeScript to generate JavaScript that in cases just wrappes Bash-Scripts and in the extend being manifested in Yaml... Uh gosh!
-
Embed this notice
pluhmen (pluhmen@kanoa.de)'s status on Tuesday, 04-Mar-2025 04:28:20 JST pluhmen
@jwildeboer Forgejo as SCM is as it is good to go for those simple things I'd like to accomplish.
But when it comes to the runners implementation, that are heavily leaning on how GitHub runners are working, I got some concerns, especially when batteries are not included and you whether have to oversee those many JavaScript Actions or left alone on reinventing the basic wheels...
-
Embed this notice
pluhmen (pluhmen@kanoa.de)'s status on Tuesday, 04-Mar-2025 03:10:49 JST pluhmen
@badnetmask Basically it's the "podman create" command taking so long. The HW it's running on is quiet old, two spinning disks in a RAID 1.
But putting this aside, I don't want to pull or use such overloaded images. And as coming from GitLab basic functions like checkout and push to the built-in package registry should be included.
Shifting this general logic to the backend makes pipeline description very sleek and so much easier to read.
Anyhow, testing Forgejo will go on.
-
Embed this notice
pluhmen (pluhmen@kanoa.de)'s status on Tuesday, 04-Mar-2025 03:10:47 JST pluhmen
@badnetmask In the last company I worked, the GitLab instance was on a on premise (VM), managed by a partner company and I just deployed GL k8s runners on one of our clusters, so the workflow was mainly based on different (partially plain upstream) container images, no need to build/use an all-in-one image nor to craft images on our own to run 3rd party ready to go software. I really liked that approach.
-
Embed this notice
pluhmen (pluhmen@kanoa.de)'s status on Monday, 03-Mar-2025 07:21:41 JST pluhmen
@jwildeboer I tested Forgejo the last two days at home. First as Container (Podman), but Git over SSH is a problem, as long as you don't want to use a different port for it. So I spun up a KVM Machine with a dedicated IP, works well as expected. Though I had to install the binary by downloading it manually and had to take care of the service untit running.
The runner has been installed the same way, but as a different user. One problem, to get podman via user socket running, aka rootless 1/3
-
Embed this notice
pluhmen (pluhmen@kanoa.de)'s status on Monday, 03-Mar-2025 07:21:40 JST pluhmen
@jwildeboer Today I've played a bit with their implementation of GH Actions and I'm not convinced that this will work for me. To checkout the git repo, you're forced to use a huge node container image (node:20-bookworm) ending in over 1 minute of initialisation, if you want to have the workflow in a container. But what's then, if you e.g. want to just run a binary encapsulated in a different container image? Artifacts, Cache, Volume Mounting, what makes the wf manifest even more verbose. 2/3
-
Embed this notice
pluhmen (pluhmen@kanoa.de)'s status on Thursday, 30-May-2024 07:03:11 JST pluhmen
Das was in #Sylt passiert ist, ist kein Einzelfall, das Spiel wird bereits gespielt, was sich dort unbeholfen verteilte, ist feste Einstellung.
Die Nazis haben Geld, Waffen, sind organisiert, hier ist die Spitze des Eisbergs zum viralen Video geworden.
Es gibt eine Querfront aus extremen Rechten, Reichen, und Leuten die gern dabei wären, weil arm und abgegangen. Was sie eint ist der Traum von mehr Nationalismus zu ihrem finanziellen Vorteil.
Der Rechtsstaat muss endlich handeln!
-
Embed this notice
pluhmen (pluhmen@kanoa.de)'s status on Tuesday, 06-Feb-2024 07:02:40 JST pluhmen
@AnthroBlogger Deine Domain ist bei 1api.net registriert. Die Nameserver (NS) Records zeigen aber auf *.wordpress.com
Ich denke du redest da mit den falschen, m.E.n. müsstest du die NS Records bei 1api.net auf den neuen Provider setzen.