For pagekite.net, I am currently experimenting with bootstrapping and configuring servers using shell scripts built/configured using a #jinja static site generator.
If this works well (so far, it does), it replaces #Ansible ...
Servers are assigned an unguessable URL, from which they download both initial bootstrapping, updates and config. The web server is 100% static.
A sweet touch: while developing, the files just live on my laptop and are downloaded over #pagekite. Because why not?
You don’t need Java to manage #Java. Ansible — #Python-based, agentless, & event-driven—handles provisioning, config, & even JVM state.
Romain Pelisse shows how @Ansible & AAP manage Java across edge and datacenter nodes: https://javapro.io/2025/10/08/put-events-in-the-driver-seat-to-manage-your-java-anywhere/
My first big personal #Ansible project was a success.
Had some hiccups that I had to diagnose and get fixed, but everything appears to be working just fine.
I'm in the final stretch now and should hopefully have something to announce tomorrow!
So #GitHub support got back to us. They are blaming a 10M commit made 2 years ago for the 404s we started experiencing a few months ago. For one, it's only 10M ffs. For two, all we did was refactor the paths and organise some #Ansible roles into sensibly grouped sub-folders. Lesson: do not refactor the paths in your application if you're on GitHub, everything will break 18 months later. Nice.
The fix, they say, is remove that commit. The fix, says I, is to migrate to #GitLab. So long, suckers.
So, do I win this week's batshit crazy #ansible playbook task award?
I've been writing relatively simple #ansible playbooks to install a demo environment and required tidbits therein for upcoming talks and forced myself to use 2.19
I'm pleasantly surprised; I was a bit scared of it.
Before running off to upgrade, do read the Ansible-core 2.19 Porting Guide
https://docs.ansible.com/ansible/latest/porting_guides/porting_guide_core_2.19.html
If you want to try the different #Fediverse #Applications like @peertube @pixelfed @Mastodon @bookwyrm @funkwhale @mobilizon etc., but you're to lazy to click an account for each applications, checkout https://infinito.nexus . With #SSO you have one Login to "rule them all" ;)
You can also use #InfinitoNexus to setup your whole #ActivityPub #ITInfrastructure #OnPremise(as long as you use it #nonprofit).Just download https://s.infinito.nexus/code and run the #ansible script.
#sysAdmin #Niche #Ansible #Debian
Utiliser des paquetages de Debian unstable via Ansible : https://www.bortzmeyer.org/ansible-debian-unstable.html
I used to use #ansible's community.digitalocean on a quite regular basis, and others might also.
Heads up! It's might be placed upon the removal list.
I think the hardest thing for me to convey to students learning #ansible is one of the points in the Ansible best practices document:
"Generous use of whitespace to break things up, and use of comments (which start with ‘#’), is encouraged."
I even explain that the use of the large key on the keyboard with which an empty line is created is almost free of charge to use!
Today at 17:00Z (19:00 Amsterdam/Paris/Berlin) will be the first #Ansible Virtual Meetup
https://forum.ansible.com/t/ansible-virtual-meetup-october-2025-2025-10-02/44538
Nach Upgrade auf #Debian Trixie/ #Ansible 2.19.2 fährt ein Teil meines Playbooks (become: true ist gesetzt) an den Baum: nämlich jener, der daemon-reload (systemd) machen soll. "Connection timed out" bzw. "Access denied". Auf dem Client sehe ich, dass genau dieser eine Aufruf mit #polkitd hantiert (alle anderen tun das nicht) & sich an der Stelle ein "FAILED to authenticate to gain authorization for action..." kassiert. Kann mich bitte wer in die richtige Richtung in Sachen Debugging schubsen?