Almost ported to ansible. Would not say it is a “clean” port because qubes ansible still lacks native tooling so there is still some shell ![]()
Great ! don’t worry shell is still better than this crap salt as hell.
tell me when I can test to help you
So can you share the code ? Then I can start implementing it
Here is a good ansible setup for some inspiration. It is not mine.
oh thanks. analyzing it right now.
NEWS: This repo looks promising. There is not many features, but the LLM stack itself is nice.
Found another one as well, contains split-ssh/split-gpg/vault and many more: GitHub - fepitre/qubes-ansible-collections · GitHub
Well, once I finish with QWT i am back on Liteqube, I have a lot of ideas how to minimize dom0 influence you guys hate so much.
Hi @arkenoi.
So you’re the developer of liteqube?
So then, I wonder if you ever plan to incorporate it together with @linuxuser1’s Live mode script and also @abdullah’s hardening script which I’ve been testing whenever I set aside the time.
Possibly. Not everything belongs, but some parts may.
@arkenoi I searched through your liteqube repo and I did not see it set expert-mode 1 on the created qubes. That could be a good idea to make it way easier to launch disposable debug consoles for headless qubes: qvm-features – manage domain’s features — Qubes Admin client mm_e2665176-0-ge266517 documentation
Thanks to @parulin for making me aware of this setting existing.
was not aware of this either! however, the whole way how we split and template x11 looks very imperfect for me, so I was going to rework this part after i finish the qwt-ng speedrun ![]()
hi does this still work in 2026? i notice the creator said “Please note I currently do not have time to maintain Liteqube, it is not updated to support Qubes 4.2” does it still work anyway?
you are looking at wrong repo. yes it does.
thank goodness where is the right one?
there’s a good link.
A post was merged into an existing topic: Updates failing?
seems really nice bc i have only 16gb of ram but does it add more attack surface since u need to put it in dom0?
Not really. There are just a few very stripped down services running in dom0 like notifications – and some of them could be substituted with native 4.3 services already shipped. The rest is one-time scripts, resizing volumes, updating templates, configuring rpc.
Ah, I guess it’s time for me to give Liteqube another try… on the spare.
@arkenoi : any caveats? or a fresh 4.3.1 install will just work with the scripts?
Most likely, did not touch it for a while so things could drift a bit. Let me know if you bump into any problem. I am running it on up to date 4.3 now, but the installation happened quite a long time ago.
whats the difference between liteqube and minimal templates?