ansible-tasmota VS Ansible

Thanks, I'm going to look into this some more. I'm starting to collect quite a few tasmota devices that need a lot of config changes when deployed, so it would be nice to centrally manage all of the local device settings. Someone did write an Ansible role to manage Tasmota configs, though.

IBM -> RedHat -> Ansible (https://docs.ansible.com/platform.html)

I think the new ansible docs are opaque, and the new "everything is an ansible collection" scheme makes troubleshooting any issues reported by users hundreds of times harder than "the old days"

I keep this (https://github.com/ansible-community/ansible-build-data/blob...) bookmarked because it's the only way to match up what "ansible 8.1.0" (https://pypi.org/project/ansible/8.1.0/) even means since it for damn sure not any of this: https://github.com/ansible/ansible/releases (they used to have a 'release' pinned on that releases tab saying "these are not the droids you are looking for"). I believe I tried asking for them to update the completely erroneous pypi "source code" link to point to that repo and ... well, one can see how well that turned out

On Monday, July 10, 2023, all RST source for Ansible community documentation will move from ansible/docs/docsite to the ansible/ansible-documentation repository. If you want to find out more or have any concerns, come let us know in the docs channel on Matrix.

I created an ansible role for i2pd. Basically, this allows system administrators who want to take part in the I2P network to automate i2pd deployment.

This change will take place on July 10, 2023. As a result, all RST source for Ansible community documentation will move from ansible/docs/docsite to the ansible/ansible-documentation repository. If you have any comments or concerns, please join us in the docs channel on Matrix and give us your feedback.

Other popular DevOps tools include Docker, Jenkins, and Ansible. Docker is a platform that allows developers to package applications and their dependencies into containers that can be easily deployed to any environment. Jenkins is an open-source automation server that enables developers to automate the building, testing, and deployment of software. Ansible is an open-source automation tool that enables developers to automate the configuration and management of IT infrastructure.

This might be a good start: https://github.com/ansible/ansible

We've been around a while, and while automation is clearly central, we have a variety of statements like "a radically simple IT automation system", "Automation for everyone", or "open-source automation that is simple, flexible, and powerful". We called out "fragmentation" in the community strategy, and this is a great example of it in action - we're not being consistent in our message.

- NMS / NPM: NetXMS, Zabbix, LibreNMS, PRTG - NCM, updates, automation: Unimus - IaC / automation: Ansible - DCIM / IPAM: NetBox - IPAM / DDI: Infoblox

Alternatively, using a tool like Ansible (available in Portage as app-admin/ansible) to manage configuration in a declarative manner can help as well.