I find that I really like using an immutable distro with a custom image (built with github actions).

So I can really separate the system-level changes (in the image, version-controlled) from my user changes.

It's a nixos-like experience without using nix at all.

There have been a couple of things to have in mind, with my Bazzite installation, for creating users or adding groups for example, this pointed me to use systemd-sysusers but it was simple.

▲

ashikns 4 days ago | parent | next [-]

I've been wanting to do this! The plan was to modify the Bazzite DX version build script, but ultimately Fedora being base was a deal breaker for me. With KDE Linux this might finally be a dream come true.

	▲	LelouBil 3 days ago \| parent [-]
		It seems like KDE linux uses a different way to provide a system image than ostree on Fedora Silverblue, so I have no idea how easy it is to make changes on top of. But for Bazzite (and other universal blue distros) you better use BlueBuild https://blue-build.org/ In the end it's an OCI container image, so you could technically just have a Dockerfile with "FROM bazzite:whatever" at the top, but bluebuild automates the small stuff that you need to do on top of it, and allows you to split your config in files. You can have a look at my repository to see how easy it is ! https://github.com/LelouBil/Leloublue

▲

gchamonlive 3 days ago | parent | prev [-]

Yeah... At this point I would give into Nix for managing the underlying arch system. It's not a gentle learning curve I believe, but at least the community is strong around nix

	▲	LelouBil 3 days ago \| parent [-]
		That's what I use too on Bazzite, custom image for system level stuff, and home-manager for user-level stuff. The nice thing about Fedora Silverblue's model is that it is literally a container image, so to "build" your image you can run any arbitrary commands, so it's way simpler than nix.