mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Serverstatistik:

1,4 Tsd.
aktive Profile

#gitlab

8 Beiträge8 Beteiligte0 Beiträge heute

I highly recommend Obtainium. It is a great way of installing and updating applications onto your Android phone. Instead of being a central store, you add the source for each project (from Github, Gitlab, Codeberg, etc) for the applications you use. It is the only "store" I added on my GrapheneOS phone. It allows absolute granular control of what I choose to install from the source; true digital intentional-ism.

Main: obtainium.imranr.dev/
Source: github.com/ImranR98/Obtainium

Also, here is a list of "complex applications" to make it easier to add them to Obtainium: apps.obtainium.imranr.dev/

#Obtainium#FOSS#Android

Den Mac mini mit M2 mal wieder aus dem Schrank geholt und als Server aktiviert.

Mal schauen wie gut macOS als Server (headless) funktioniert.

Was schon gut ist, dass man mit reinen Boardmittel via Remote Desktop darauf zugreifen kann.

Bisher sogar ohne AppleID am laufen.

Werde ihn jetzt als GitLab Runner nutzen. Bisher hat sich ein Server bei Hetzner die größte Zeit dafür gelangweilt.

Lässt sich auch gut im Homelab betreiben, da der Runner auf den GitLab Server zugreift, um die Jobs abzuholen.

#server#macmini#apple

That cost me a lot of nerves, but now I can see the light at the end of the tunnel again.

Unfortunately I couldn't solve the problem in #codeberg, I created an issue and am now back in #gitlab.

And here is my clone of the #gluon samples HelloFXML project with gitlab-ci pipeline.
gitlab.com/naturzukunft_de/jav

The generated artifact of the pipeline can be found here.
gitlab.com/naturzukunft_de/jav

The apk is now also running on my FP 5 with e/OS.

Thanks to @pat_dev for his support

GitLabnaturzukunft / javaFX / HelloFXML · GitLabGitLab.com

Temporary migration of our projects to GitLab

We have recently started migrating our projects to GitLab as a result of GitHub not fixing our issue of GitHub Actions workflows not running due to hidden non-payment of $0. This migration allows us to not only restore our CI/CD pipelines for our builds, but it also allows us to continue making quality products as we’ve always promised you from the beginning of the year.

GitLab is an open-source software that allows you to manage your repositories for your open-source projects, and hosts various options, such as issues, pipelines, and more. Meanwhile, GitHub is a proprietary software that does the same thing, and is owned by Microsoft.

We have recently started our migration to GitLab by importing almost all repositories (archived or not) from our official GitHub account. While the main repositories get automatically updated by pushes to GitLab, our repositories that are located there don’t get updated by pushes to their GitHub counterparts. We recommend starting all pull requests in the GitLab repositories instead.

This was done in response to GitHub’s lack of support for such issues for GitHub Actions, considering the severity of the issue, and several people have faced this issue as you can see in this discussion. This is going to be temporary, while GitHub fixes this problem, which should happen soon.

All links will be updated to point to GitLab to let users know of our new (and temporary) place for our projects while a fix is incoming.

#github#GitLab#Migration

I just posted to my blog -- "Storing SSH Private Keys in GitLab CICD variables": When storing an SSH private key in GitLab CICD variables I encountered a strange error: "Unable to create masked variable because: The value cannot contain the following characters: whitespace characters." -- Read more here: dfoley.ie/blog/storing-ssh-pri -- #linux #gitlab #ssh #POSSE

www.dfoley.ieStoring SSH Private Keys in GitLab CICD variablesWhen storing an SSH private key in GitLab CICD variables I encountered a strange error: "Unable to create masked variable because: The value cannot...

Das ist so feist, dass meine Abteilung jetzt doch vom eher etwas rudimentären Mattermost-Kanban zum Gitlab-Issue-Management umgezogen ist.

Sehr schön auch, dass alle in der Abteilung damit einverstanden waren, dass alle aus dem Haus mit Gastrolle (erlaubt Kommentare in Tickets und Mentions) alles sehen dürfen. So eine Haltung ist nicht selbstverständlich.

Das macht so Spaß.

A job in a #GitLab pipeline ran into a rather cryptic error, mentioning mapping values in a specific line.

After some initial head-scratching, the error was found. Inside a string, used by the echo command, colons were used. These were interpreted as "key: value" and led to the #pipeline error.

claudiokuenzler.com/blog/1494/

Claudio Kuenzler · Solving GitLab pipeline error (): mapping values are not allowed in this contextVon Claudio Kuenzler
Antwortete im Thread

So far, some organisations are differentiating themselves by having nothing to do with the #MOLE Training craze. Or developing modest, fully libre versions of the tech in-house, for a few specific features appropriate to its few strengths (eg auto-translation). When the bubble finally bursts (soon, perhaps?), these orgs will come out of it with their credibility intact.

Meanwhile those that leaned into the hype will have to rebuild theirs from scratch. Looking at you @gitlab.

#GitLab

@jbz

Fortgeführter Thread

And yes, whoever uses #discord for #documentation and #versioning instead of a goddam #git [doesn't have to be @github / #GitHub or @gitlab / #GitLab or @Codeberg / #Codeberg or even @gitea / #Gitea - just use any git and write down your documentation in a useable format like #Markdown or goddamn ASCII plain text FFS] should be banned for life from #coding, working in #IT or contribute to #FLOSS.

  • Because it's literally worse than people shitting "#Ai" #Slop all over the place cuz that can be fixed faster and easier by backrolling said commits and banning the offender!

youtube.com/watch?v=9ehLMlVTRJ

Fortgeführter Thread

I made this crontab to keep your #btrfs based #gitlab runner happy without to much maintenance.

Should keep you from running out of disk space.

5 0 1,15 * * smartctl -t short /dev/sda
5 1 1,15 * * btrfs scrub start /
5 4 1,15 * * btrfs filesystem defrag -r /
5 0 2,16 * * btrfs balance start -musage=50 /
5 4 2,16 * * btrfs balance start -dusage=10 /
5 0 3,17 * * docker image prune -a