home.social

#ansible — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ansible, aggregated by home.social.

  1. Since I re-image my Linux desktop so often, I have given a great deal of thought to preserving and re-creating my configurations.

    So I wrote a single bash file to rule them all, sort of.

    My script, `dot`, creates a tiny CLI Ansible installation, and interactively helps write a short Ansible playbook that defines symlinks, install scripts and Python environments.

    I download the script and run `./dot --help` to get started. Use `dot check` to review selections, and `dot apply` to ensure localhost is configured with them.

    Because it uses Ansible under the hood, it doesn't do unecessary work, it provides detailed output, and it creates a file with a full definition of the configuration in a well know standard (which can always be re-used later, even without my script.)

    If you add `dot` to your own `dotfiles` repository, and organize yours like mine (`files`, `installs` and `reqs`) then `dot` will use find your folders and offer to link your files, run your install scripts, or create your Python environments.

    codeberg.org/EdTheDev/dotfiles

    #linux #macos #bash #cli #localhost #config #ansible

  2. Since I re-image my Linux desktop so often, I have given a great deal of thought to preserving and re-creating my configurations.

    So I wrote a single bash file to rule them all, sort of.

    My script, `dot`, creates a tiny CLI Ansible installation, and interactively helps write a short Ansible playbook that defines symlinks, install scripts and Python environments.

    I download the script and run `./dot --help` to get started. Use `dot check` to review selections, and `dot apply` to ensure localhost is configured with them.

    Because it uses Ansible under the hood, it doesn't do unecessary work, it provides detailed output, and it creates a file with a full definition of the configuration in a well know standard (which can always be re-used later, even without my script.)

    If you add `dot` to your own `dotfiles` repository, and organize yours like mine (`files`, `installs` and `reqs`) then `dot` will use find your folders and offer to link your files, run your install scripts, or create your Python environments.

    codeberg.org/EdTheDev/dotfiles

    #linux #macos #bash #cli #localhost #config #ansible

  3. Ansible Vault sicher und komfortabel nutzen: In unserem neuen Blogbeitrag zeigt Jens Meißner, wie sich Secrets mit GnuPG verschlüsselt speichern und über den GnuPG-Agent bequem verwenden lassen – ganz ohne unverschlüsselte Passwortdateien.

    ➡️ b1-systems.de/ansible-secrets-

    #Ansible #DevOps #Linux #GnuPG

  4. Ansible Vault sicher und komfortabel nutzen: In unserem neuen Blogbeitrag zeigt Jens Meißner, wie sich Secrets mit GnuPG verschlüsselt speichern und über den GnuPG-Agent bequem verwenden lassen – ganz ohne unverschlüsselte Passwortdateien.

    ➡️ b1-systems.de/ansible-secrets-

    #Ansible #DevOps #Linux #GnuPG

  5. Ansible Vault sicher und komfortabel nutzen: In unserem neuen Blogbeitrag zeigt Jens Meißner, wie sich Secrets mit GnuPG verschlüsselt speichern und über den GnuPG-Agent bequem verwenden lassen – ganz ohne unverschlüsselte Passwortdateien.

    ➡️ b1-systems.de/ansible-secrets-

    #Ansible #DevOps #Linux #GnuPG

  6. Ansible Vault sicher und komfortabel nutzen: In unserem neuen Blogbeitrag zeigt Jens Meißner, wie sich Secrets mit GnuPG verschlüsselt speichern und über den GnuPG-Agent bequem verwenden lassen – ganz ohne unverschlüsselte Passwortdateien.

    ➡️ b1-systems.de/ansible-secrets-

    #Ansible #DevOps #Linux #GnuPG

  7. Ansible Vault sicher und komfortabel nutzen: In unserem neuen Blogbeitrag zeigt Jens Meißner, wie sich Secrets mit GnuPG verschlüsselt speichern und über den GnuPG-Agent bequem verwenden lassen – ganz ohne unverschlüsselte Passwortdateien.

    ➡️ b1-systems.de/ansible-secrets-

    #Ansible #DevOps #Linux #GnuPG

  8. Since I have the day off, of course I woke up early with a code fix stuck in my head for my attempt at cleaning up my Linux configuration repository (dotfiles).

    Now my (sort of) all-in-one-script dotfiles organizer can also babysit my Python virtual environments (using Ansible, of course.)

    codeberg.org/EdTheDev/dotfiles

    #linux #foss #bash #script #python #ansible #devops #localhost #orchestration

  9. Since I have the day off, of course I woke up early with a code fix stuck in my head for my attempt at cleaning up my Linux configuration repository (dotfiles).

    Now my (sort of) all-in-one-script dotfiles organizer can also babysit my Python virtual environments (using Ansible, of course.)

    codeberg.org/EdTheDev/dotfiles

    #linux #foss #bash #script #python #ansible #devops #localhost #orchestration

  10. 🎧 Your ears called. BitFlip picked up.

    📻 Ep. 8 — Just Install it on the Host

    We dig into the NVIDIA RTX Spark and what it means for local AI, revisit the Proxmox-vs-Unraid debate through Alex's Perfect Media Server Part 3, and do a deep dive on Jellyfin's strengths, rough edges, and the upcoming version 12.

    #bitflipshow #Nvidia #LocalAi #Llm #Proxmox #Arm #Unraid #Mergerfs #Snapraid #Ansible #Jellyfin

    🔗 bitflip.show/8

  11. 🎧 Your ears called. BitFlip picked up.

    📻 Ep. 8 — Just Install it on the Host

    We dig into the NVIDIA RTX Spark and what it means for local AI, revisit the Proxmox-vs-Unraid debate through Alex's Perfect Media Server Part 3, and do a deep dive on Jellyfin's strengths, rough edges, and the upcoming version 12.

    🔗 bitflip.show/8

  12. Finished up getting Telegraf installed on all the VMs and getting the Influx Debian repo mirrored locally. All of the config/install stuff is in Ansible and the deployment went pretty smoothly. I now officially have all of the data coming into Influx which is nice.

    #homelab #monitoring #influx #ansible

  13. Finished up getting Telegraf installed on all the VMs and getting the Influx Debian repo mirrored locally. All of the config/install stuff is in Ansible and the deployment went pretty smoothly. I now officially have all of the data coming into Influx which is nice.

    #homelab #monitoring #influx #ansible

  14. # Bare-metal Kubernetes на 5 VM: Calico IPIP + MetalLB + GitOps — честный опыт с граблями

    Поднял Kubernetes кластер на 5 VM с нуля на VMware: Calico IPIP, MetalLB, GitOps через ArgoCD, PostgreSQL HA. Три неочевидные проблемы которые съели много времени — MTU и TLS, нестабильный BGP на VMware, конфликты git push в GitOps.

    habr.com/ru/articles/1041356/

    #kubernetes #devops #ansible #gitops #argocd #calico #metallb #prometheus #cicd

  15. Well. I had to reinstall my computer (long story, stupid nvidia) so this time I installed #OpenCode on my computer, hooked it up to the qwen3.5 model at #Scaleway and added the VSCode integration. I am rather blown away. It's like having a really fast junior dev working for me. I asked it to read the code of the project and complete a simple role for #Ansible, which it did well, but made some odd module selections. I corrected it, it spat out the code I wanted. Like, 30 seconds and it's done.

  16. Well. I had to reinstall my computer (long story, stupid nvidia) so this time I installed #OpenCode on my computer, hooked it up to the qwen3.5 model at #Scaleway and added the VSCode integration. I am rather blown away. It's like having a really fast junior dev working for me. I asked it to read the code of the project and complete a simple role for #Ansible, which it did well, but made some odd module selections. I corrected it, it spat out the code I wanted. Like, 30 seconds and it's done.

  17. Well. I had to reinstall my computer (long story, stupid nvidia) so this time I installed #OpenCode on my computer, hooked it up to the qwen3.5 model at #Scaleway and added the VSCode integration. I am rather blown away. It's like having a really fast junior dev working for me. I asked it to read the code of the project and complete a simple role for #Ansible, which it did well, but made some odd module selections. I corrected it, it spat out the code I wanted. Like, 30 seconds and it's done.

  18. pi@pi0:~ $ ansible all -i hosts -m shell -a "docker system prune -a -f --volumes" --become

    Just freed up over 1.6 Gigabytes of disk space

    That's two years' worth of junk from messing about. 🤣

    #Clusterhat #DockerSwarm #Ansible

  19. pi@pi0:~ $ ansible all -i hosts -m shell -a "docker system prune -a -f --volumes" --become

    Just freed up over 1.6 Gigabytes of disk space

    That's two years' worth of junk from messing about. 🤣

    #Clusterhat #DockerSwarm #Ansible

  20. For those who are wondering why my projects are so silent, I moved to my own Forgejo instance at code.spoljarevic.sh

    From there I will continue my journey.

    Tho I didn’t have lots of time to work on them, and they will slightly change.

    Due to an upcoming server migration, new tools and my personal life, everything got slow.

    But I already finished some open issues on the Ansible Project and will go into testing after my vacation.

    It shall be finished this month or I’m no longer trusting myself.

    Next month will be nothing since I’m gonna focus on chess openings and the month after I’m working on a Knowledge Base (fork of hyprland wiki)

    After that, everything should go normal again.

    #ansible #archlinux #project #forgejo #server #ServerMigration #wiki #KnowledgeBase #chess #chessopenings

  21. For those who are wondering why my projects are so silent, I moved to my own Forgejo instance at code.spoljarevic.sh

    From there I will continue my journey.

    Tho I didn’t have lots of time to work on them, and they will slightly change.

    Due to an upcoming server migration, new tools and my personal life, everything got slow.

    But I already finished some open issues on the Ansible Project and will go into testing after my vacation.

    It shall be finished this month or I’m no longer trusting myself.

    Next month will be nothing since I’m gonna focus on chess openings and the month after I’m working on a Knowledge Base (fork of hyprland wiki)

    After that, everything should go normal again.

  22. 24 Debian LTS Advisories fixing 250 CVEs for various packages were released by Debian LTS contributors in March 2026. These include notable security updates for ansible, asterisk, gimp, gst-plugins-base1.0, gst-plugins-ugly1.0, imagemagick, libpng1.6, linux kernel, roundcube, strongswan and more.

    In addtion to the LTS contributions, the team also prepared updates for recent releases - Debian 12(#bookworm), Debian 13(#trixie) and Debian unstable.

    Read the full report at freexian.com/blog/debian-lts-r

    This work is funded by Freexian's Debian LTS offering. Become a sponsor of Debian LTS (freexian.com/lts/debian/?utm_s) and enjoy the benefits (freexian.com/lts/debian/detail)

    #debian #debianlts #freexian #ansible #imagemagick

  23. @nickbearded i think older cheap pc platform is probably better value once prices crash and they will eventually selling the sw but also the hw you know it runs really well on is a key uniter point and then you have the total package, repeat for pihole, open source pineapple, kismet, ssl/tls proxy, squid caching proxy, web server and lamp stack, etc dedicated monitoring and analytics is another, central logging is another #bashcore modules #extensions #plugins #sbom #reproducible builds #ansible playbooks

  24. @nickbearded i think older cheap pc platform is probably better value once prices crash and they will eventually selling the sw but also the hw you know it runs really well on is a key uniter point and then you have the total package, repeat for pihole, open source pineapple, kismet, ssl/tls proxy, squid caching proxy, web server and lamp stack, etc dedicated monitoring and analytics is another, central logging is another #bashcore modules #extensions #plugins #sbom #reproducible builds #ansible playbooks

  25. @vivekanandanks thanks for the interesting post. I want to suggest that the #configmanagememt analogy part (where #ansible sits, and so do several other widely used tools like #saltstack, #puppet, #chef, #cfengine) can be improved. The central premise of configuration management is that current state is dynamic, a moving target. Constantly pruning a growing tree might be a better analogy.

  26. AWX: большой рефакторинг и потеря корпоративных функций — что происходит с проектом

    Для многих технических специалистов AWX на протяжении многих лет был синонимом «бесплатного Ansible Tower» — надёжным и функциональным решением для управления Ansible-автоматизацией. Это был стандарт де-факто для тех, кто хотел получить удобство (практически) "коробочного" решения и функциональность корпоративного уровня, не вкладываясь в лицензии коммерческого решения. Однако 2 июля 2024 года вышел релиз AWX версии 24.6.1, который стал последним на данный момент выпуском проекта. С тех пор прошло более полутора лет, а новых релизов так и не появилось. В репозитории проекта на GitHub висит предупреждение: «Releases of this project are now paused during a large scale refactoring». Для сообщества, активно использующего или планирующего использовать AWX как основной инструмент централизованного управления Ansible-автоматизацией, эта ситуация вызывает закономерные вопросы: Что происходит с проектом? Есть ли у него будущее? Для конечного пользователя не совсем очевидно, но AWX не умирает, а кардинально трансформируется. В данной статье мы разберем текущую ситуацию вокруг AWX, опираясь на официальные анонсы, технические дискуссии разработчиков и статусы ключевых проектов. Проанализируем архитектурные изменения проекта. Разберемся, почему эти изменения были неизбежны, что именно было «вырезано» из проекта и что всё это значит для вас — инженеров ИТ инфраструктуры и архитекторов автоматизации, которые используют AWX в своей работе и проектах.

    habr.com/ru/companies/astralin

    #ansible #awx #eventdriven #it_automation #Infrastructure_as_a_Code_IaC #configuration_management #devops #astra_automation #network_automation

  27. AWX: большой рефакторинг и потеря корпоративных функций — что происходит с проектом

    Для многих технических специалистов AWX на протяжении многих лет был синонимом «бесплатного Ansible Tower» — надёжным и функциональным решением для управления Ansible-автоматизацией. Это был стандарт де-факто для тех, кто хотел получить удобство (практически) "коробочного" решения и функциональность корпоративного уровня, не вкладываясь в лицензии коммерческого решения. Однако 2 июля 2024 года вышел релиз AWX версии 24.6.1, который стал последним на данный момент выпуском проекта. С тех пор прошло более полутора лет, а новых релизов так и не появилось. В репозитории проекта на GitHub висит предупреждение: «Releases of this project are now paused during a large scale refactoring». Для сообщества, активно использующего или планирующего использовать AWX как основной инструмент централизованного управления Ansible-автоматизацией, эта ситуация вызывает закономерные вопросы: Что происходит с проектом? Есть ли у него будущее? Для конечного пользователя не совсем очевидно, но AWX не умирает, а кардинально трансформируется. В данной статье мы разберем текущую ситуацию вокруг AWX, опираясь на официальные анонсы, технические дискуссии разработчиков и статусы ключевых проектов. Проанализируем архитектурные изменения проекта. Разберемся, почему эти изменения были неизбежны, что именно было «вырезано» из проекта и что всё это значит для вас — инженеров ИТ инфраструктуры и архитекторов автоматизации, которые используют AWX в своей работе и проектах.

    habr.com/ru/companies/astralin

    #ansible #awx #eventdriven #it_automation #Infrastructure_as_a_Code_IaC #configuration_management #devops #astra_automation #network_automation

  28. AWX: большой рефакторинг и потеря корпоративных функций — что происходит с проектом

    Для многих технических специалистов AWX на протяжении многих лет был синонимом «бесплатного Ansible Tower» — надёжным и функциональным решением для управления Ansible-автоматизацией. Это был стандарт де-факто для тех, кто хотел получить удобство (практически) "коробочного" решения и функциональность корпоративного уровня, не вкладываясь в лицензии коммерческого решения. Однако 2 июля 2024 года вышел релиз AWX версии 24.6.1, который стал последним на данный момент выпуском проекта. С тех пор прошло более полутора лет, а новых релизов так и не появилось. В репозитории проекта на GitHub висит предупреждение: «Releases of this project are now paused during a large scale refactoring». Для сообщества, активно использующего или планирующего использовать AWX как основной инструмент централизованного управления Ansible-автоматизацией, эта ситуация вызывает закономерные вопросы: Что происходит с проектом? Есть ли у него будущее? Для конечного пользователя не совсем очевидно, но AWX не умирает, а кардинально трансформируется. В данной статье мы разберем текущую ситуацию вокруг AWX, опираясь на официальные анонсы, технические дискуссии разработчиков и статусы ключевых проектов. Проанализируем архитектурные изменения проекта. Разберемся, почему эти изменения были неизбежны, что именно было «вырезано» из проекта и что всё это значит для вас — инженеров ИТ инфраструктуры и архитекторов автоматизации, которые используют AWX в своей работе и проектах.

    habr.com/ru/companies/astralin

    #ansible #awx #eventdriven #it_automation #Infrastructure_as_a_Code_IaC #configuration_management #devops #astra_automation #network_automation

  29. Comprehensive comparison of Ansible, Puppet, Chef, and SaltStack for configuration management. Explore architecture, performance, features, and ideal use cases to choose the right tool for your infrastructure automation needs.

    #Ansible #Puppet #Chef #SaltStack #Configuration Management

    dasroot.net/posts/2026/02/ansi

  30. Comprehensive comparison of Ansible, Puppet, Chef, and SaltStack for configuration management. Explore architecture, performance, features, and ideal use cases to choose the right tool for your infrastructure automation needs.

    Management

    dasroot.net/posts/2026/02/ansi

  31. Bạn đang muốn tự động hoá, tái tạo và tài liệu hoá toàn bộ cấu hình server (cài Docker, triển khai Traefik + các ứng dụng container) và có thể dry‑run cài đặt trước khi đưa vào thực tế? Ansible + Docker Compose là giải pháp phổ biến, giúp ghi lại mọi bước (cài Docker, thiết lập mạng, triển khai image) dưới dạng mã, dễ mở rộng và kiểm thử nội bộ. #selfhosted #docker #ansible #traefik #automation #tựđộng #container #cauhinh #devops

    reddit.com/r/selfhosted/commen

  32. Bạn đang muốn tự động hoá, tái tạo và tài liệu hoá toàn bộ cấu hình server (cài Docker, triển khai Traefik + các ứng dụng container) và có thể dry‑run cài đặt trước khi đưa vào thực tế? Ansible + Docker Compose là giải pháp phổ biến, giúp ghi lại mọi bước (cài Docker, thiết lập mạng, triển khai image) dưới dạng mã, dễ mở rộng và kiểm thử nội bộ. #selfhosted #docker #ansible #traefik #automation #tựđộng #container #cauhinh #devops

    reddit.com/r/selfhosted/commen

  33. Hey #NeoVim users, how many plugins are you currently using?

    I just realized, all told I have roughly 70 installed and configured (though much of that is from LazyVim). I use nvim for essentially everything I can, but lately it's a lot of #Python, #Ansible, #bash, #hcl, #markdown. (just normal sysadmin stuff)

    Things still feel quite snappy and I really do use most of them actively. But it got me curious what everyone else has cooking.

    #NeoVim #LazyVim #Plugins #Poll #Extensions #VSCodeSucks #sysadmin #Linux #IDE

  34. # Evolving Our Tor Relay Security Architecture

    blog.emeraldonion.org/evolving

    A new blog post where @alexhaydock goes into some detail showcasing our minimalistic @alpinelinux Tor relays architecture, a threat model, and including a link to our now-public open source "Emerald Relays" orchestration framework.

    The past 6 months have proven its success, and now we look forward to phase 2 (read the post!), which we need your help in funding. Emerald Onion is a U.S. 501(c)(3) tax-deductible nonprofit, so please consider donating before 31 December! emeraldonion.org/donate/

    #Tor #TorOps #Privacy #AntiCensorship #Anonymity #Ansible #Proxmox #Terraform #AMD #Epyc #SEVSNP #NonProfit #GivingTuesday

  35. # Evolving Our Tor Relay Security Architecture

    blog.emeraldonion.org/evolving

    A new blog post where @alexhaydock goes into some detail showcasing our minimalistic @alpinelinux Tor relays architecture, a threat model, and including a link to our now-public open source "Emerald Relays" orchestration framework.

    The past 6 months have proven its success, and now we look forward to phase 2 (read the post!), which we need your help in funding. Emerald Onion is a U.S. 501(c)(3) tax-deductible nonprofit, so please consider donating before 31 December! emeraldonion.org/donate/

    #Tor #TorOps #Privacy #AntiCensorship #Anonymity #Ansible #Proxmox #Terraform #AMD #Epyc #SEVSNP #NonProfit #GivingTuesday