ruhr.social

Martin (he/him)looks nice to get a quick overview of codebase <a href="https://gitdiagram.com/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gitdiagram.com/</a>. Do you know something similar for <a href="https://hachyderm.io/tags/gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitlab</a> projects?

Jan Wildeboer 😷:krulorange:<a href="https://social.wildeboer.net/tags/Gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gitlab</a> already locked out users from mainland China, Macao and Hong Kong back in January, deleting accounts in February this year, BTW, in case you think they are an alternative.<a href="https://forum.gitlab.com/t/question-about-the-gitlab-can-no-longer-service-in-mainland-china-macao-and-hong-kong/120085" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://forum.gitlab.com/t/question-about-the-gitlab-can-no-longer-service-in-mainland-china-macao-and-hong-kong/120085</a>2/3

Johannes KastlHere you are: Vagrant-Setup with Ansible deploying k3s and GitLab inside k3s.<a href="https://codeberg.org/johanneskastl/gitlab_on_k3s_vagrant_libvirt_ansible" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codeberg.org/johanneskastl/gitlab_on_k3s_vagrant_libvirt_ansible</a> <a href="https://github.com/johanneskastl/gitlab_on_k3s_vagrant_libvirt_ansible" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/johanneskastl/gitlab_on_k3s_vagrant_libvirt_ansible</a>Currently without the Runner, that comes next.<a href="https://digitalcourage.social/tags/GitLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitLab</a> <a href="https://digitalcourage.social/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevOps</a> <a href="https://digitalcourage.social/tags/k3s" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#k3s</a> <a href="https://digitalcourage.social/tags/kubernetes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kubernetes</a> <a href="https://digitalcourage.social/tags/Ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ansible</a> <a href="https://digitalcourage.social/tags/vagrant" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vagrant</a> <a href="https://digitalcourage.social/tags/hellyeah" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hellyeah</a>

Johannes Kastl<a href="https://mastodon.social/@jwolynko" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jwolynko</a> When it comes to on-prem, GitLab still seems to be the preferred solution (GitHub enterprise seems to be deprecated, thank the universe for that). I personally am running Forgejo wherever possible.But most of the customers I know do run some form of GitLab. And I wanted to make sure I had a working test setup, whenever I need one. Currently I wanted to do some testing for GitLab runners on Kubernetes.The package based ones are pretty simple to setup (not talking about maintenance, of course).<a href="https://codeberg.org/johanneskastl/gitlab_vagrant_libvirt_ansible" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codeberg.org/johanneskastl/gitlab_vagrant_libvirt_ansible</a> <a href="https://codeberg.org/johanneskastl/gitlab_and_runner_vagrant_libvirt_ansible" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codeberg.org/johanneskastl/gitlab_and_runner_vagrant_libvirt_ansible</a><a href="https://digitalcourage.social/tags/GitLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitLab</a> <a href="https://digitalcourage.social/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevOps</a> <a href="https://digitalcourage.social/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kubernetes</a> <a href="https://digitalcourage.social/tags/vagrant" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vagrant</a> <a href="https://digitalcourage.social/tags/Ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ansible</a>

Johannes Kastl<rant> OK, so however thought up the structure of the <a href="https://digitalcourage.social/tags/Gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gitlab</a> helm chart was ... creative, to put it politely.The chart itself has dependencies, as is common with helm charts. But it also has a charts directory, which contains 5 other charts. Including one called gitlab. Which again has a charts directory as well as dependencies.So, depending on which chart you want to configure, it might be chart-name.something or gitlab.chart-name.something. Oh, they also use global.something or global.chart-name.something.And as this is not creative enough, some charts are installed if chart-name.install is true. For some it is chart-name.enabled...But help is near, there is an operator, that does the heavy lifting for you. Oh wait, it uses the values from the helm chart of its CRD... </rant><a href="https://digitalcourage.social/tags/GitLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitLab</a> <a href="https://digitalcourage.social/tags/devops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devops</a> <a href="https://digitalcourage.social/tags/helm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#helm</a> <a href="https://digitalcourage.social/tags/kubernetes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kubernetes</a> <a href="https://digitalcourage.social/tags/why" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#why</a>

:gnu:HackerQué bien eso de que haya repositorios Git libres y gratis para publicar tu código en Internet. GitHub comenzó a funcionar en el año 2008.A día de hoy si respetas un poco tu trabajo utilizarías sitios basados en <a href="https://masto.es/tags/GitLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitLab</a> o <a href="https://floss.social/@forgejo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@forgejo</a> como <a href="https://social.anoxinon.de/@Codeberg" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Codeberg</a>

MikaIt's pretty stupid that you could neither name a <a href="https://sakurajima.social/tags/GPG" rel="nofollow noopener noreferrer" target="_blank">#GPG</a> key registered to <a href="https://sakurajima.social/tags/GitLab" rel="nofollow noopener noreferrer" target="_blank">#GitLab</a>, or see which may have expired. My key has expired, I've renewed it locally, and now am updating it on both <a href="https://sakurajima.social/tags/GitHub" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> and GitLab. On GH, it's easy to know which key I'd have to replace since it lets you know which of them has expired, and when registering it for the first time, you have to give it an identifier. On GL, there's no (human) identifier whatsoever, and it doesn't tell you which of them has expired either. Better find a way to identify it correctly tho or you might risk deleting the wrong GPG key, and potentially cause your verified commits to be deemed unverified. --- Edit: Figured it out. When you list your GPG key on your system like this: <pre><code>gpg --list-secret-keys --keyid-format long</code></pre> and get something like this: <pre><code>/home/user/.gnupg/pubring.kbx ------------------------------ sec ed25519/1H89FHO4MGAJTJ9Z 2024-01-15 [SC] [expires: 2026-01-15] 0A41C9F6335DBF47A1A186FAC82F22229FCCE1BF</code></pre> While on GH, you can identify your key either through the 1) name you gave it or 2) the "short key" i.e. <code>1H89FHO4MGAJTJ9Z</code>, on GL you identify it through its "long key" i.e. <code>0A41C9F6335DBF47...</code>. Likewise, on GH, it tags each "Key ID" and "Subkey" as <code>Expired</code> if they're expired - easy enough to understand, meanwhile on GL, it tags valid, non-expired keys as <code>Verified</code>, which may be somewhat confusing or vague.. especially when users coming into this setting is either adding a new GPG key or renewing an outdated one.

PloneMikel Larreategi <a href="https://mastodon.eus/@erralin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@erralin</a> of <a href="https://codesyntax.com" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codesyntax.com</a> shows how to Deploy Cookieplone Based Projects With GitLab CI/CD <a href="https://plone.social/tags/plone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#plone</a> <a href="https://plone.social/tags/plone6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#plone6</a> <a href="https://plone.social/tags/wpd2025" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wpd2025</a> <a href="https://plone.social/tags/CMS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CMS</a> <a href="https://plone.social/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a> <a href="https://plone.social/tags/React" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#React</a> <a href="https://plone.social/tags/volto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#volto</a> <a href="https://plone.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://plone.social/tags/community" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#community</a> <a href="https://plone.social/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevOps</a> <a href="https://plone.social/tags/GitLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitLab</a> <a href="https://plone.social/tags/CICD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CICD</a> <a href="https://youtu.be/7d1KQSXpodY" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://youtu.be/7d1KQSXpodY</a>

Christian M. Grube 🐧<a href="https://social.tchncs.de/tags/gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitlab</a> 17.10.4, 17.9.6, 17.8.7 releasedSecuritypatch<a href="https://social.tchncs.de/tags/adminlife" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#adminlife</a> <a href="https://social.tchncs.de/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> <a href="https://social.tchncs.de/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://about.gitlab.com/releases/2025/04/09/patch-release-gitlab-17-10-4-released/?utm_medium=mastodon" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://about.gitlab.com/releases/2025/04/09/patch-release-gitlab-17-10-4-released/?utm_medium=mastodon</a>

SheogorathFinally merged my <a href="https://microblog.shivering-isles.com/tags/Tekton" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tekton</a> experiment.Added 34000 lines of YAML to drop 62. Not the best ratio 😅But let's see where things go from here. I'm quite confident that I'll be able to replace gitlab-runners in the next few weeks and find a good pattern for the pipelines.But I think I'll take a day off working on these. It's so crazy abstract, but that's also the potential tekton holds.<a href="https://git.shivering-isles.com/shivering-isles/infrastructure-gitops/-/commit/ee0d4e8e2230930973be8bd96021dcba087af463" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://git.shivering-isles.com/shivering-isles/infrastructure-gitops/-/commit/ee0d4e8e2230930973be8bd96021dcba087af463</a><a href="https://microblog.shivering-isles.com/tags/kubernetes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kubernetes</a> <a href="https://microblog.shivering-isles.com/tags/gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitlab</a>

Florian LohoffOkay - so found the sidekiq job - its running - no due mails ... I dont get it.<a href="https://c.im/tags/gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitlab</a>

Florian LohoffHelp <a href="https://c.im/tags/gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitlab</a> I still searching for an issue where in multiple gitlab instances no emails beeing sent out for "due" issuesMail notification works generally, but the morning routine of due issues is not sent out anymore. It used to work, but its dead jim.sidekiq is running - i dont see any obvious errors. I fail to find the name of the job responsible for sending out the due messages so i cant check if the job is scheduled.This is all 17.8.6-ce.0

Marcel SIneM(S)USVor 20 Jahren rief <a href="https://social.tchncs.de/tags/LinusTorvalds" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LinusTorvalds</a> <a href="https://social.tchncs.de/tags/git" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#git</a> :git: ins Leben – bis heute ein großer Erfolg | Developer <a href="https://www.heise.de/news/Sicher-schnell-flexibel-und-ohne-Alternative-git-wird-20-Jahre-alt-10340325.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.heise.de/news/Sicher-schnell-flexibel-und-ohne-Alternative-git-wird-20-Jahre-alt-10340325.html</a> <a href="https://social.tchncs.de/tags/GitLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitLab</a> <a href="https://social.tchncs.de/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> <a href="https://social.tchncs.de/tags/BitBucket" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BitBucket</a>

ClaytonI have to reference <a href="https://freeradical.zone/tags/gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitlab</a> merge request and issue numbers a lot while doing dev stuff for <a href="https://freeradical.zone/tags/postmarketOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#postmarketOS</a> and <a href="https://freeradical.zone/tags/alpinelinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#alpinelinux</a> (like for giving to our mrtest tool), so I made a simple bookmarklet that will copy this number to my clipboard:<a href="https://gitlab.postmarketos.org/-/snippets/10" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gitlab.postmarketos.org/-/snippets/10</a>Bookmarklets are neat!

Scott Williams 🐧Tried to login to <a href="https://mastodon.online/tags/Gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gitlab</a> today. The OTP code they sent to my email (which landed in Spam) didn't work and further login attempts, the code never arrived and now my account is locked, even if logging in through GitHub, etc, and the login page for their Zendesk also doesn't load for me to submit a ticket, so that's fun. I'm remembering again why I opted for deploying <a href="https://mastodon.online/tags/Forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forgejo</a> over it.

Prof. Dr. Dennis-Kenji KipkerUnd ein weiterer Vorfall reiht sich in die lange Reihe von <a href="https://chaos.social/tags/Databreaches" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Databreaches</a> ein - dieses Mal wohl beim Mietwagenanbieter <a href="https://chaos.social/tags/Europcar" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Europcar</a> und erneut über <a href="https://chaos.social/tags/Gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gitlab</a>. Sollte sich der Verdacht bewahrheiten, ist nicht nur der Autovermieter von einem massiven <a href="https://chaos.social/tags/Cybervorfall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Cybervorfall</a> betroffen, sondern ebenso dessen Kunden:"Europcar hat den Angaben nach bereits bestätigt, dass tatsächlich Daten des Unternehmens abgeflossen sind."<a href="https://www.golem.de/news/datenleck-kundendaten-und-quellcode-von-europcar-abgeflossen-2504-195077.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.golem.de/news/datenleck-kundendaten-und-quellcode-von-europcar-abgeflossen-2504-195077.html</a> <a href="https://chaos.social/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a>

Janik :linux: :ansible: :bash:Over the coming months I will move all my personal and private repositories from <a href="https://fosstodon.org/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> and <a href="https://fosstodon.org/tags/GitLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitLab</a> to <a href="https://fosstodon.org/tags/Codeberg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Codeberg</a>. I run many static sites and intend to use <a href="https://ci.codeberg.org" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://ci.codeberg.org</a> to trigger the builds.Once this process is finished and everything works fine with <a href="https://fosstodon.org/tags/forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#forgejo</a>. I will also migrate the repos of my company <a href="https://fosstodon.org/tags/MintSystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MintSystem</a> to <a href="https://www.codey.ch/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.codey.ch/</a>. As there are some GitHub integrations I can't get rid of, I intend to mirror back the repos.I'll keep you updated via <a href="https://fosstodon.org/tags/CodebergMigration" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CodebergMigration</a>.

Arty-chan (Cynthia)Cool. 20th anniversary of <a href="https://mastodon.social/tags/git" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#git</a> and <a href="https://mastodon.social/tags/GitLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitLab</a> celebrated with an interview with Linus Torvalds: <a href="https://about.gitlab.com/blog/2025/04/07/celebrating-gits-20th-anniversary-with-creator-linus-torvalds/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://about.gitlab.com/blog/2025/04/07/celebrating-gits-20th-anniversary-with-creator-linus-torvalds/</a>

InfoQGitLab Duo with Amazon Q is here! This integration of Amazon Q Developer with GitLab brings generative AI capabilities directly into GitLab, helping developers with feature development, code upgrades, reviews, and unit testing.Learn more: <a href="https://bit.ly/4jql9Qb" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://bit.ly/4jql9Qb</a> <a href="https://techhub.social/tags/InfoQ" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#InfoQ</a> <a href="https://techhub.social/tags/GitLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitLab</a> <a href="https://techhub.social/tags/AmazonQ" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AmazonQ</a> <a href="https://techhub.social/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a> <a href="https://techhub.social/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareDevelopment</a>

David PapeOK everyone, I did it. I started a blog. 😅 It has a welcome post and a small tip on sorting your emails from Git forges. More to come soon. Feel free to check it out!<a href="https://www.zyzzyxdonta.net/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.zyzzyxdonta.net/</a><a href="https://social.tchncs.de/tags/Indieweb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Indieweb</a> <a href="https://social.tchncs.de/tags/Blogging" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Blogging</a> <a href="https://social.tchncs.de/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> <a href="https://social.tchncs.de/tags/GitLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitLab</a> <a href="https://social.tchncs.de/tags/Codeberg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Codeberg</a> <a href="https://social.tchncs.de/tags/Git" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Git</a> <a href="https://social.tchncs.de/tags/Forge" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forge</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#gitlab