silverblue-nix VS devbox

On silverblue, you just follow this guide and it uses a systemd service that uses the command chattr to make / immutable (temporary) but not the reclusive directories (that means only / not the contents inside the directories) by doing chattr -i / creates /nix and /var/lib/nix mkdir /nix mkdir /var/lib/nix then it bind mounts it mount --bind /var/lib/nix /nix then it uses chattr again to make / immutable again chattr +i / . The problem with microos is that the chattr command can't change atributes on the / directory. But is there like a way to have a /nix subvolume like how there is writable /var and /home subvolumes? Like how can you make it not part of the immutable part. you can go into the transactional update shell and type mkdir /nix and /nix is there but is not writable. Is there a way to make a subvolume and mount it as /nix and have it readable and writable?

agreed with that I only install drivers, distrobox, and qemu/virt manager on the immutable part and everything else is done with either flatpak, containers, or nix (it works on silverblue quite well. there is a guide for it)

fedora silverblue is good if you want a reliable system. you can also get traditional package management by using containers from distrobox or toolbox or you can use nix on silverblue

I find it quite useful for silverblue. I can install packages user wide or system wide without the need to layer packages. It gives me a mutable eviroment while keeping the core system safe. Proot isn't available for fedora but it is available with nix so I can have proot system wide with nix which is not possible with podman. Applications with nix start way faster than starting a podman container. It is quite useful. only downside is that you need to set SELinux to permissive (which really isn't an issue for me) there is a guide for installing nix on silverblue too.

Installing nix, you would have to disable selinux and if you use silverblue, you have to do these extra steps. it would be nice if all you got to do is type sudo dnf install nix (or sudo rpm-ostree install nix if you are on silverblue) and it would automaticly add selinux policies and automaticly have the .desktop files in ~/.nix-profile/share/applications or ~/nix/var/nix/profiles/default/share/applications for system wide automaticly show up in the DE launcher and also have sudo work with nix better. it should also work for workstation and silverblue too.

maybe install it on toolbox, distrobox, or even nix if you want to install something that isn't a flatpak. nix is good for installing other terminals, shells, and fetch programs so I don't need to layer. it also supports user wide and system wide packages. only downside is that you need to disable selinux.

you should give nix on silverbluea try

here is a guide to install it on silverblue https://gitlab.com/ahayzen/silverblue-nix

the nice thing is you can install nix package manager on other distros. it is very useful to use different shells and using neofetch without layering on silverblue. there is a guide for it

Never mind traditional package managers... you plug it in right, you can run Nix on Silverblue!

https://gitlab.com/ahayzen/silverblue-nix

NixOS people will prefer NixOS, but Silverblue seems like a nice complement to Nix if you need an FHS base system and want to retain some Nix-ish features like rollbacks and atomic upgrades.

Before I went on my Christmas vacation last year I wrote an article on how I use Nix in my Elm projects. At the time, I was pleased with my set up. However, not even a month would go by before my satisfaction was questioned. In early January, Carlo Ascani asked a question, on the Elm Discourse, about his Umbra project. I decided to explore his project and I soon discovered two files, devbox.json and devbox.lock, I had never seen before. This piqued my curiosity and I had to learn more. I followed the link to the Devbox website and feverishly read the docs. I... was... hooked. I was pleasantly surprised by its simplicity and it seemed to fit my use cases really well.

How does Flox compare to Devbox? https://github.com/jetpack-io/devbox

I've spent the last year managing all my packages with Devbox (https://github.com/jetpack-io/devbox).

Local dev, cloud dev, CI, production – all with the same config file. Fingers crossed my talk submission for PackagingCon gets accepted. It'd be awesome to share this new way of working with a wider audience.

> Now to figure out what a "flake" is…

Flake is a worthwhile addition to Nix that is worth learning. But like anything Nixian, it's not straightforward.

Have you checked out any of the tools that aim to simplify Nix experience? We built Devbox (https://github.com/jetpack-io/devbox) with this in mind.

Also devbox ( https://github.com/jetpack-io/devbox ) which is what this is for does not work on windows because of its Nix dependency.

For these reasons, I believe most developer environments should prioritize developer experience over fidelity. Tools like Containerized development environments and cloud emulators can strike the right balance and there’s no surprise that we see increased activity around devcontainers, and similar solutions.

Local first, cloud optional is the only way (IMHO) we're going to get people off their local laptop development setups.

We need to support local dev environments first, with the exact same config a developer can then move to the cloud.

See https://github.com/jetpack-io/devbox for how this can be achieved and https://www.mikenikles.com/blog/dev-environments-in-the-clou... for my thoughts after 3 years of working in this space.

If you like the properties of Nix, but find it confusing, you should check out Devbox! It simplifies the process of creating Nix-powered dev environments:

https://github.com/jetpack-io/devbox

As part of the work we've been doing with [devbox](https://github.com/jetpack-io/devbox), we needed a unit testing framework to test some of our nix code. Unfortunately we had some use cases where we did *not* want to introduce a dependency on `nixpkgs` (and therefore we couldn't use `runTests`).