#NixOS is interesting. Pretty reliable (not as much as #AtomicDesktops in my noob tests) while also performant
Note that such old hardware will have #microcode vulnerabilities and locking it down will further slow it down. At least thinking of #spectre or #meltdown (not sure if hyperthreading was even thought of back then)
#nixos moderators are useless and calling that out isn’t wrong
@pmidden So this is kinda like using aptitude instead of apt-get on a Debian distro? It still connects to the real nix repos, with their godlike rolling schedules and whatnot?
I'm what you might call a conservative about this sort of thing - I'm not against these side versions, but as long as the majority of the community is using regular nix, the most likely scenario is that I'm gonna stay there as well, strictly because it is easier to find help and guidance from the largest user community.
As long as they are not giving up essential things for their mainstream choice, of course, and it seems to me that nix decides what's mainstream.
I remain a highly enthusiastic #NixOS user but I know I am not the first to complain about their atrocious documentation practices. I am still working on fully understanding the beast, but once I do I expect I'll try to help out with that, as my main contribution.
Main thing is nixos.wiki has to fucking go. It's just fucking embarrassing.
@zenbrowser I just upgraded on #NixOS, let's see.
@korenchkin Is nixos.wiki managed by non-NixOS or NixOS-hostile personnel?
Cause I tell ya, letting that link above just exist, with not so much as a "HEY DON'T READ THIS GO TO THE ONE AT NIXOS.ORG YOU NUMPTY" or something like that is pretty newbie-hostile.
Not just bad or clumsy management, but actively hostile. I dunno how much of my time that site just wasted, or how much it will waste before it is eradicated from the earth.
Oh how I do love the docs at #NixOS.
I am attempting to do the "System wide vim/nvim configuration" example at https://nixos.wiki/wiki/Vim and rebuild is giving me this error:
error: attempt to call something which is not a function but a set
I read on one forum that removing the { } you see there, the set in question, from the override line, that would fix it, but then I of course get
error: expected a set but found a function
Since this is coming straight from the wiki and my syntax is correct, this is what you might call
Annoying
I made an interactive treemap visualization tool for Nix derivations!
Check it out :D
I got a #nixos tempban, glad to see the mods are fighting the good fight
Account suspended until April 4, 2025: tempban
Ok so I guess #ZFS and #NixOS seem to go together okay, I don't use it to boot, but at this moment I'm taking it on faith that I will either be able to create my volumes and set my mountpoints the way I have always and will always do it, or else that the NixOS way to do it will become clear once I'm up against it, which so far is what always happens.
I had high hopes for running @yunohost on this particular box, but there's just waaaaay too many weird problems trying to make it play nice with Cloudflare tunnels, including lots of "hey this is not very supported" in the docs. I don't want to receive this sort of traffic at my front door (real IP addy with firewall ports open) so now that I've kinda wrapped my brain around using a #CDN via tunnel, I'm pretty dead set on it.
Very open to considering other CDNs though, I have heard some things I cannot recall exactly about CF.
Yesterday the #H2O web server #NixOS module merged into #Nixpkgs with #HTTP3 / #QUIC support to be super easy.
An example of a simple reverse proxy usage, with compression + ACME + HTTP/2 + HTTP/3 + TLS redirect + Mozilla recommended TLS settings, would look like:
services.h2o = {
enable = true;
settings = {
compress = "ON";
http2-reprioritize-blocking-assets = "ON";
ssl-offload = "kernel";
};
hosts."example.org" = {
tls = {
policy = "force";
quic = { };
recommendations = "modern";
};
acme.enable = true;
settings = {
paths."/" = {
"proxy.reverse.url" = "http://127.0.0.1:42069";
};
};
};
}
@Natanox @matthias Finde ich auch. Bin jetzt bei #NixOS gelandet, wo sich alles sehr schön integrieren (auch mit https://gethomepage.dev) und verwalten lässt (alle services und settings reproduzierbar in configfiles). Ist ein massives und schmerzhaftes rabbithole
aber lohnt sich sehr, wenn es einmal klickt.
@mahmoudajawad @codemonkeymike My apologies, I didn’t see your comment!
I’ve got a Surface Pro 6 that I tested out the surface kernel on with #NixOS. Like I had mentioned in an earlier comment, I highly recommend building your new NixOS configuration that includes the surface kernel on a more powerful desktop and allowing the awesome remote deployment feature of #nix to deploy it to the Surface…
https://guide.deuxfleurs.fr/prise_en_main/
Créer un LAN chez soi derrière un FAI (en utilisant NixOS)
#nixos #deuxfleurs #lan #autohebergement #nodatacenter #association #admin #devops
Ideas that you get when walking off to blow out steam: I'll just build a VM inside Proxmox, and try to replicate all the services from one of my Raspberry Pi. If it works, I'll put it in production.
#HomeLab #Proxmox #Nix #nixOS #RaspberryPi
NixOS Meetup in Darmstadt on April 7th, 2025!
Join us for great discussions and networking. Open to all! Location: Chaos Computer Club Darmstadt e.V., Wilhelminenstr. 17, 64283 Darmstadt
See you there! #NixOS https://discourse.nixos.org/t/nixos-meetup-darmstadt-2025-04-07/62264
#nixos has anyone else seen the security tab lol