#Semaphore #Semaphores #Traffic

Ich habe die Tage mal #semaphore aufgesetzt, das ist ein echt cooles Tool um #Ansible Playbooks von einer Weboberfläche heraus zu starten.
Man kann dort auch geplante Aufgaben einstellen und so Dinge automatisieren.

Ein paar Merge Requests für die Doku von ansible semaphore erstellt. Ich mag Semaphore, aber die Doku ist ausbaufähig
Mit all den offenen Doku Merge Requests, die der anderen und meiner, dürfte die Doku deutlich besser werden. Auch wenn es nicht meine Doku ist, freue ich mich, sollten alle MRs demnächst gemerged werden :)

I finally eliminated the need for a dedicated #thread controlling the pam helper #process in #swad.

The building block that was still missing from #poser was a way to await some async I/O task performed on the main thread from a worker thread. So I added a class to allow exactly that. The naive implementation just signals the main thread to carry out the requested task and then waits on a #semaphore for completion, which of course blocks the worker thread.

Turns out we can actually do better, reaching similar functionality like e.g. #async / #await in C#: Release the worker thread to do other jobs while waiting. The key to this is user context switching support like offered by #POSIX-1.2001 #getcontext and friends. Unfortunately it was deprecated in POSIX-1.2008 without an obvious replacement (the docs basically say "use threads", which doesn't work for my scenario), but still lots of systems provide it, e.g. #FreeBSD, #NetBSD, #Linux (with #glibc) ...

The posercore lib now offers both implementations, prefering to use user context switching if available. It comes at a price: Every thread job now needs its private stack space (I allocated 64kiB there for now), and of course the switching takes some time as well, but that's very likely better than leaving a task idle waiting. And there's a restriction, resuming must still happen on the same thread that called the "await", so if this thread is currently busy, we have to wait a little bit longer. I still think it's a very nice solution.

In any case, the code for the PAM credential checker module looks much cleaner now (the await "magic" happens on line 174):
https://github.com/Zirias/swad/blob/57eefe93cdad0df55ebede4bd877d22e7be1a7f8/src/bin/swad/cred/pamchecker.c

Wer einen ganzen Zoo von Servern, VMs und/oder Kleinstcomputern verwaltet, sehnt sich schnell nach einem Werkzeug, dass einem ein paar Aufgaben abnimmt.

Eines ist #Ansible und mit einem vorgeschalteten #Semaphore lässt es sich auch noch gut automatisieren. Eine Installationsanleitung kann ich jetzt im Blog auch beitragen:

Automatisierte Aktualisierungen mit Semaphore/Ansible

#Linux #Admin

https://www.jcs-net.de/blog/automatisierte-aktualisierungen-mit-semaphore-ansible

#Semaphore #Semaphores #Traffic

FLOSS Weekly Episode 825: Open Source CI With Semaphore - This week, Jonathan Bennett and Ben Meadors talk to Darko Fabijan about Semaphore,... - https://hackaday.com/2025/03/19/floss-weekly-episode-825-open-source-ci-with-semaphore/ #hackadaycolumns #flossweekly #semaphore #podcasts #ci/cd

#Semaphore #CICD platform went Open Source #devops #sre https://github.com/semaphoreio/semaphore

Absolutely loving my Social Media life these days.
As I say to many, your mileage may differ. I think it all comes down to who you chose to engage with, and the topics you reply to.
We all have the choice to be on certain services and not on others. We should all abide and respect the choices others make in this regard.

My main Social Media area these days is the Fediverse, particularly through a GoToSocial ActivityPub instance named Polymaths.social. Wonderful software, instance, admin, and neighbours!
Since 2009 I was on a Mastodon instance named LinuxRocks.online. It started off really well with good chats on the local timeline. However, over the past year certain people and their followers came in, the local chats got strained, and quite painful at times, and I knew I needed to move on. I was friendly with the owner, and moderators, but the time had come.

To access Polymaths.social I use Phanpy on a browser, and Tusky on my Android Phone.
For browser access I did use Semaphore for a while. Very clean and effective, but Phanpy is like KDE vs Mate. To me this is a good thing. I do use Semaphore at times to check on Follow Requests and to currently "Delete and Redraft" as needed.

Telegram is a large part of my life. I use it to talk with many friends, including Arianna and my Sister Catriona, podcrawl and Linux groups, as well as my own Christian group.

I'm still on Facebook, and yes I question that daily.
For now I am there.
As I said at the start, this is my choice, and I am there for really good friends, family, and groups.

A few weeks ago I activated my Instagram account, which had been set up for no follows and privates, just so I could view content as needed.
I was getting so many requests from good friends if I was on there, and ok... "caved in", but my involvement is relatively minimal. Mostly posting my own photos and commenting on those of friends.

Well, that's my online life, and it is good.
Feel free to reply back with questions, and DM as needed.

#SocialMedia #Fediverse #GoToSocial #Mastodon #ActivityPub #Phanpy #Tusky #Semaphore #Telegram #Facebook #Instagram

Is there some built-in option that I could use to make Semaphore UI send an email alert when a scheduled playbook task has ‘changed’, as opposed to only if it has failed?

I realize I could bake it into the playbook as another task, just curious if there’s another option I’m not seeing within Semaphore.

Does anyone know if there's an actively maintained fork of the @pinafore / @semaphore fediverse web app?

I just set layout.css.backdrop-filter.enabled to false in about:config on #Firefox and suddenly, #Pinafore / #Semaphore profiles are snappy and fast instead of highly laggy and causing the CPU to heat up quickly and the fan to spin up.

Apparently, the implementation of filter effects in Firefox is extremely bad and unperformant (and needs constant redoing on scrolling and whatever).

Primer episodio de Accesibilidad con Tecnologías libres tras el cambio de instancia (relevante para el Podcasting 2.0)

Producido por @raivenra , tenemos las siguientes secciones:

· Odisea en el ciberespacio, con David Marzal @DavidMarzalC .
· Accesibilidad web, con Pablo Arias.
· Otros mundos, otras realidades, con Thais Pousada.
· Clases con Pascal, con David Pacios
· Érase una vez, con Enrique Varela @evarela .
· Diseño para todos, con Jonathan Chacón @jonathanchacon .

Enlaces, reproductor y más info en:
https://accesibilidadtl.gitlab.io/11

- Feed: https://accesibilidadtl.gitlab.io/feed

CC: @eva_m

#AccesibililidadTL #AccesibilidadConTecnolgiasLibres #a11y #ATL

#Phanpy #Semaphore #ElkZone #Mona #Pachli #Tusky #Tweescake #TWBlue
#BuscaApps #URA #Mapcesible #Joomla #TalentosInclusivos

Du hättest gerne eine simplere, aufgeräumtere Oberfläche für Mastodon? Probier's mal mit #Semaphore! Unter https://semaphore.pnpde.social kannst du die auf Einfachheit und Geschwindigkeit optimierte Mastodon*-Oberfläche benutzen

* funktioniert auch mit vielen anderen Fediverse-Servern

“Last month #legislation quietly passed the federal #parliament that will allow for the storage and disposal of #NuclearWaste at the #Adelaide shipyard in #Osborne, which is 25 kilometres north-west of the city's #CBD and near the popular seaside suburb of #Semaphore and historic Port #Adelaide.”

#Labor / #AUKUS
<https://www.abc.net.au/news/2024-11-18/aukus-nuclear-waste-to-be-stored-adelaide-suburbs/104605640>