22
Plasma and Ansible on enterprise thin clients
(discuss.kde.org)
KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.
If you encounter a bug, proceed to https://bugs.kde.org, check whether it has been reported.
If it hasn't, report it yourself.
PLEASE THINK CAREFULLY BEFORE POSTING HERE.
Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.
I'm not using Ansible myself, but I do use
kreadconfig
andkwriteconfig
, and well, it does just have 4 parameters to identify a setting and its value, so that Ansible module does look like it's sufficient for that.One tip I have, is that you can figure out which GUI setting corresponds to which config file change, by setting up a Git repo in
~/.config
and looking at the diff. So, basically:When you're done transferring that into Ansible, you can commit or stage the changes and tweak another UI setting, or if you're completely done, then just
rm ~/.config/.git/
.I guess, you could also use this Git repo to roll back all the settings and see if your Ansible automation works as expected.
Unfortunately, this will be a thin client so it’s gonna need to have predefined defaults. I could use skel, but I wanna be able to change settings for defaults and pre-existing profiles.