Using #Ansible to fix our #Puppet Agents after their agent certificates have expired.

Why not? :)

New Project - digitalprivacy.homes

A “side” project called digitalprivacy.homes is currently underway. This side project has grown much faster than I had anticipated. Some of you may have already noticed..
It is intended for home use only and provides several tools for protecting ...

Read more here:
https://digitalprivacy.diy/news/en/new-project-digitalprivacy-homes

Proxmox fully automated! From ClickOps to Code: Automated. Audited. Revisioned. Repeatable.

Starting from the base by automating:
- Cluster initialization
- Cluster join
- Storage Integration
- Proxmox Backup Server Integration
- SDN Networks (different ones for pros/dev)
- Guest Resources utilizing the cluster infrastructure

#Proxmox #PVE #Pbs #ProxmoxBackupServer #opensource #Automation #Ansible #python #devops #terraform #cicd #pipeline #cluster #nfs #iscsi

https://peertube.gyptazy.com/w/4cp7ddLdSHGSUeUwUPsuo9

When we originally invented #ansible’s “ansible_managed” variable, we made it configurable. Before the default was broken a few years ago, it was roughly:

ansible_managed = Ansible managed: {file} modified on %Y-%m-%d %H:%M:%S by {uid} on {host}

One of the cool bits (I say this as its inventor) was that such an entry in an ansible.cfg caused the templated value to have the filename of the template source {file}, it’s owner {uid}, and it’s modification time in the strftime() patterns.

1/2

#Ansible scheduled a virtual #Meetup on October 2nd.

Sign up here:

https://www.meetup.com/ansible-virtual-meetups/events/310258600/

Ever wondered which SSH keys are lurking on your servers?

Just published a comprehensive Ansible playbook in my gists that audits your entire infrastructure for SSH keys and finds dangerous unprotected private keys!

- Detects unprotected private keys
- Lists all Pubkeys for root and users
- Comprehensive reporting (TXT + CSV)

https://codeberg.org/Larvitz/gists/src/branch/main/2025/20250804-SSHKeyAuditPlaybook.md

#Linux #hivemind

TL;DR: How would you deploy a maintainable Linux build to 14 PCs?

I have a lab network of 14 PCs at $dayjob. I want them all to have the same Linux build/image, with the same apps - (probably) Plasma, VirtualBox, LibreOffice, Packet Tracer (so JRE as well) as the basics, plus various other tools.

If the users mess up the machine somehow, they need to be easily re-imaged. It would be nice if /home could optionally be preserved, but not essential.

I am currently the most Linux-savvy person in the team that will be looking after these PCs. I'm not there all the time, so this needs to be maintainable by techies who don't daily drive Arch.

I know #Ansible could be a good option, meaning I have some flexibility with which distro. (I am open to different distros for this.) #Nix or #NixOS could also work, but the learning curve for that could be pretty steep (for me - steeper for the rest of the team), plus its non-standard approach to Linux might be confusing for some.

I guess some solution using a PXE boot and then an auto-deployed script or definition file?

Hey #GetFediHired,
After some layoffs in my current company, I am looking for some #softwaredevelopment job, #remote only. I can work in the #EU or would be able to travel some weeks during the year.

I am fluent in #PHP, #Symfony, #Golang, #gRPC, #REST and #GraphQL #API, #Docker, #Ansible, Event Streaming and modern software development in general with experience of over 15 years in various roles - from senior engineer to CTO. I value good software architecture, tests, documentation in combination with valuable communication and discussions.

Find my CV here: https://www.codedge.de/cv

If that sounds like something, drop me a message or reply. Cheers!