@sullybiker Facepalm. Non-inclusive language is not the reason #Ansible does not have enough minority and female users. This can be ascertained by asking how many minorities were turned away from using Ansible because of its non-inclusive language.
I'm not saying that they should intentionally utilize offending language, or that removing it should not be a priority, but they seem to be focused on a minor part of their perceived problem instead of asking why their userbase looks the way it does.
Sometimes, it is definitely "better" to cycle by myself, particularly since most people are not very good cyclists, but I am on the bike enough that it makes sense to ride with someone.
Anyway, I am going to an #Ansible meetup tomorrow. Perhaps that will help some, although that means I won't be around to help with the cat stuff. I am sure I will come home to a mess.
Well, I guess #ansible doesn't work in a #lxc container: "ERROR! Unable to use multiprocessing, this is normally caused by lack of access to /dev/shm: [Errno 2] No such file or directory"
So this was me, at bedtime with tired/sick brain, converting my #Ansible PHP role from PHP 7.1 to 7.2, failing to upgrade an Ubuntu 17.10 server, then doing a dist upgrade on that host so I could finish the PHP rollout.
My SSH key needs some equivalent to a breathalyzer, but for rational decision making.
I've been working off-and-on about getting my linode instances managed via ansible and I'm almost to the point where I can run the scripts and not freak out.
Wondering if sysadmin ever gets to the point where you are confident.
Somehow, I am truly almost done migrating things from this #Linode into #Ansible and onto new hosts. Gitea and Drone CI really gave this years-long effort a kick in the pants these past few weeks.
Somehow, I am truly almost done migrating things from this #Linode info #Ansible and onto new hosts. Gitea and Drone CI really gave this years-long effort a kick in the pants these past few weeks.
This #Ansible playbook sample with the extended syntax for dictionaries makes me think completely different about some of my roles. They could be *much* more generic, with the config passed in the playbook. Can't wait to try this out.
@millergeek I've got some servers set up using #Ansible because there is a ton of configuration in them I want to keep documented. Docker would let me more rapidly make working servers, but I'm hesitant too move away from playbooks to dockerfiles because I can't use them to update running servers. And I have a bunch of templates for config files I would need to find some other way to template.
@musicman Some time when you're less stressed, maybe you can write something about why you chose #Chef (and what factors you considered overall) over #Ansible and #Puppet. Especially considering that the other two were in the #CentOS repos, but Chef is not.