KDE

5375 readers

90 users here now

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.

Plasma 6 Bugs

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.

founded 1 year ago

MODERATORS

carlschwan@lemmy.kde.social

Bro666@lemmy.kde.social

herzenschein@pawb.social

Aniqakhokhar@lemmy.kde.social

Plasma and Ansible on enterprise thin clients (discuss.kde.org)

submitted 4 months ago by YamiYuki@lemmy.kde.social to c/kde@lemmy.kde.social

2 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Ephera@lemmy.ml 5 points 4 months ago

I'm not using Ansible myself, but I do use kreadconfig and kwriteconfig, 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:

cd ~/.config
git init
git add .
git commit -m "original config"
# now change setting in UI
git diff

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.