Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
social.tchncs.de is one of the many independent Mastodon servers you can use to participate in the fediverse.
A friendly server from Germany – which tends to attract techy people, but welcomes everybody. This is one of the oldest Mastodon instances.

Administered by:

Server stats:

3.8K
active users

social.tchncs.de: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#gitlab

12 posts10 participants0 posts today
Public
The gallant knight

Wow, im #JavaScript #Discord-Kanal kam grad nebenbei die Frage untereinander auf "Bist Du noch auf GitHub?"
#GitHub war die letzten 15 Jahre eine Institution, ich denke die haben #OpenSource richtig nach vorne gebracht und nun geht grad alles ganz schnell den Bach runter. Menschem machen sich ernsthaft Sorgen um ihre Daten, um Machtmissbrauch und #Politik. Und es ist gut, wenn man sich z.B. #GitLab oder #codeberg anschaut. Das sind sehr gute Alternativen.
#Datenschutz

Public
Jan Jäger

Ich schätze #GitLab als Werkzeug immer mehr. 🙂

Gerade rausgefunden, dass es möglich ist, individuelle Kalender zu Issues zu abonnieren, z.B. anhand des Fälligkeitsdatums.

Und es können sogar Filter gesetzt werden, sodass die Kalender beispielsweise nur diejenigen Issues anzeigt, für die man selbst verantwortlich ist.

Mal schauen, ob eine Kollegin nun auch zu GitLab umziehen wird.

Public
June

It feels weird to have #GitLab automatically update itself using... the GitLab runner attached to GitLab. But at least now I don't have to manually keep it up-to-date for security. #devops

(There might be a shorter command to upgrade a Helm chart to the latest version, but we patch some container images and thus need to pull the app version out of the specific chart version we're upgrading to; not shown in the example script)

A screenshot of the scheduled GitLab pipeline that automatically updates the GitLab instance.
Screenshot of the upgrade script available at https://gist.github.com/hach-que/3e8d8007d73dd650b4953d71d03d418d.
Public *
Dendrobatus Azureus

I have just taken the time to thoroughly read the following article

This article has led me to the conclusion that an Open{source} War will have to be waged against LLM large language model abusers of data collection.

The work of these bots is pure DDoS denial of service. An interesting set of offensive tools have been programmed and are already implemented. They have proven to be quite effective and are being refined into sophistication to literally work to knock these networks of bots offline, in a DOT MMORPG approach.

It is unthinkable that LLM bots steal our Open Source resources servers bandwidth and financial cashflow without serious repercussions!

WTF are LLM companies thinking? Even Meta has waged war against us!

LLM has waged a brutal war.

The Open Source Community is responding; even those at The Dark Side of the internet are making tools to assist everyone against Artificial Intelligence LLM DDoS attacks, which knock whole Open Source Networks offline, as we speak.

It doesn't matter if in the end it looks like a Terminator landscape globally on the IT scale. Open source will win. LLM will disappear...

The composition is a screencap of a news article displayed on an Android device. The article's headline reads, "Open source devs say AI crawlers dominate traffic, forcing blocks on entire countries." Below the headline, a subheading states, "AI bots hungry for data are taking down FOSS sites by accident, but humans are fighting back." The author's name, Benj Edwards, and the publication date, March 25, 2025, are displayed, along with the time, 6:36 PM, and the number of comments, 147. The article's first paragraph discusses a software developer named Xe laso, who reached a breaking point when aggressive AI crawler traffic from Amazon overwhelmed their Git repository service, causing instability and downtime. Despite configuring standard defensive measures, such as adjusting robots.txt and blocking known crawler user-agents, the issue persisted. The image accompanying the article shows a person sitting on a floral-patterned couch, working on a laptop. The person is partially submerged in water, with their legs visible above the waterline. The background includes a bookshelf with books and a potted plant, and the person is wearing a dark top and blue jeans with rolled-up cuffs. The credit for the image is given to Henrik Sorensen via Getty Images. Ovis2-8B 🌱 Energy used: 0.299 Wh
#DDoS#LLM#bots
Replied in thread
Public
Johannes Kastl

@jwolynko 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).

codeberg.org/johanneskastl/git
codeberg.org/johanneskastl/git

Summary card of repository johanneskastl/gitlab_vagrant_libvirt_ansible
Codeberg.orggitlab_vagrant_libvirt_ansibleVagrant-libvirt setup with a VM that is running a Gitlab instance
#GitLab#DevOps#Kubernetes
Public
Johannes Kastl

<rant>
OK, so however thought up the structure of the #Gitlab 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>

#devops#helm#kubernetes
Continued thread
Public
Shawn Webb

From a usability perspective, the last thing to implement is a method for downloading a tarball of the repo (at a specific commit, tag, or branch). That would enable us to integrate support for distset downloading in the #HardenedBSD ports tree (similar to how #GitLab and #GitHub distset support is implemented).

Screenshot of GitLab, with the required feature highlighted.
Public
Sheogorath

Finally merged my #Tekton 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.

git.shivering-isles.com/shiver

GitLabfeat(tekton): Deploy to cluster (ee0d4e8e) · Commits · Shivering-Isles / Infrastructure GitOps · GitLabThis patch introduces Tekton pipelines and Tekton triggers to the cluster. This should provide a new, independent way to run pipelines across various git forges. It's a preparation of changing...
#kubernetes#gitlab
ExploreLive feeds
About