Is something like this defined in a standard somewhere?
Is something like this defined in a standard somewhere?
Thats what I do as well. It makes it easy to seperate between logical units.
I’m happy with Open WebUI
Can you link any good guides on transistioning to guix?
This.
However sometimes the user can’t access the device. Depending on your system, I recommend adding your user to the dialout/serial group.
I.e. quick online search
Please tell ^^
Nix has an open issue on integrating IPFS support.
There’s also an old tutorial.
+ Impermanence
Nice! I love trying out new tools. This one seems straightfoward to use.
This, or slackhq/nebula
Thanks you for the answer.
I love that you have EU options ^^
Just to make sure I understood how this works:
Can the card be refilled, or are the last few cents wasted?
You’re playing Devils Advocate, and you probaly know it xD
Anyway, I prefer NixOS for it’s declarativity, reproducibility and immutability.
Example: You want nginx with acme setup? Just tell it to, and NixOS will figure out the steps to reach the desired state.
There are also these two blog posts by elis on setting up tmpfs specifically. Though these posts rather are setup guides, than “talking about the philosophy” of systems design.
My system configuration can be found on git.sr.ht/~sntx/flake. I’ve linked the file tree pinned to the version 0.1.1 of my config, since I’m currrently restructuring the entire config[1] as the current tree is non-optimal[2].
The documentation in the README in combination with the files should cover most of what I’ve described, with the following exception: disko is not present to the repo yet, since I’ve set it up with a forked version of my config and the merge depends on finishing the restructuring of my system configuration.
The goal is to provide definitions for desktops, user-packages, system-packages, themes and users. Each system can then enable a set of users, which in turn have their own desktop, user-packages and theme. A system can also enable system-packages for itself, independent of users. If a user is enabled that has a desktop set, the system will need to have display-manager set as well, which should launch the users configured desktop. ↩︎
The current config assumes a primary user, and can only configure a single DE and apply the application/service configs only to that user. ↩︎
I’m suprised nobody mentioned nebula: A scalable overlay networking tool with a focus on performance, simplicity and security.
I’ve been running it for about two years on multiple machines and it worked flawlessly so far. Even connecting two hosts, both behind mullvad-vpn tunnels.
The only downside is, that you have to host your own discovery server (callled “lighthouses”). One is fine, but running at least two removes the single point of failure from the network.
What do you use it for? How’s the daily-driver experience?