It's this time of the year again, this weekend is #ZHF in Rapperswil.
After having participated in a few of those I was very happy when I discovered this RFC a few days ago.
https://github.com/NixOS/rfcs/blob/master/rfcs/0180-broken-package-removal.md
Miałem sobie darować #NixOS , ale tak jakoś wyszło, że skonfigurowałem go do końca XD Działa jak złoto - co prawda to nie jest mój główny komputer, ale będę sobie testował to distro dalej.
KDE z ikonkami Papirus wygląda obłędnie.
Dolphin to nadmenadżer plików.
Ogólnie KDE się ładnie wyrobiło.
Alright, well, I have a Drupal site now.
It's unavailable at the moment; I still have to set everything up.
The setup I finally got to work uses Nginx for the reverse proxy/web server and PostgreSQL for the database, both of which are set up in the traditional NixOS way. The Drupal site itself is not, though; I finally just gave up and made a directory for it, and installed it to said directory using Composer, manually.
So the site itself is the only part that isn't "reproducible" according to NixOS. I manage the site myself; it's not actually reproducible, to me, when NixOS manages it for me, because it does some kind of black magic involving symlinking directories outside of the Nix store, to the Nix store. Not all of it, though. So I didn't actually have direct access to the entire directory for the site, because that was a Nix store path, which could change at any time. This is one of those few times when I got tired of fighting NixOS and just did something normally. 
NixOS Search - Options - Sourcehut.minio
#sourcehut is the only forge for which #minio can be enabled in #nixos 25.05
https://search.nixos.org/options?channel=25.05&show=services.sourcehut.minio.enable&query=Sourcehut.minio
Updated my VPS today and it worked like a charm. Thanks #nixos
VM Adventures - Getting hands on with NixOS in the VM : Part 2 of "Building a Bulletproof Home Server" series
Learning the ropes during my 3 week saga of building a NixOs server.
I just wanna say THANK YOU to everyone here who is talking about, testing, and even contributing to the #nixbook project!
When I started this project last year, I could never imagine it being this far along and well loved by now.
#foss really is the best damn way to do software and love y'all!
The 25.11 release of Nixbook is going to be an epic one!
Die außergewöhnliche Datenlage lässt die Prognose zu, dass es am Freitag 14.11. gegen 20Uhr ein #Binärgewitter geben wird 
Wie immer mit #Livestream und #IRC Chat:
https://blog.binaergewitter.de/pages/live
Gerüchteweise mit Überraschungsgast 
#binaergewitter #livestream #nerdtalk #opensource #live #podcast #ServiceToot @makefu @madmas @l33tname @ingo @kreativmonkey
#Linux #Technologie #OpenSource #AI #KI #FreeSoftware #NixOS #Rust
You can guess now why I get angry (yes, it really is anger, or frustration) when people devise a language like Nix but DO NOT make it a Lisp.
They have cut off the ability to easily add a serious macro facility that does not disrupt text editors and pretty printers.
They have also complicated the ability to represent the language as data. They have not prevented this, of course, but they have made it more complicated.
I have suggested Nix get an hygienic (‘referentially transparent’) macro facility like Scheme’s syntax-rules, but Nix has the problem that it is not a Lisp. It COULD HAVE BEEN a Lisp as easily as it is what it is, but it is not.
Thus nixfmt would be befuddled by the macro facility.
Otherwise I see no problem with the suggestion.
For instance, people have difficulty with writing recursive functions. What if they could use something like Scheme’s ‘named let’ macro? It would be easier.
RE: https://masto.ai/@chemoelectric/115533048166888164
You can see here an example of what is meant by ‘macro’ in the context of Scheme or Common Lisp. It is not the same thing as is meant by ‘macro’ in C.
It means extending the syntax of the language. Here to add Nix as sublanguage.
In C it is rare to use macros to alter the syntax of the language, although VERY occasionally it is done. To do so creates problems for C, though, because unlike Lisp it is not ‘still s-expressions’.
(BTW C does NOT have macros. It needs a preprocessor.)
`systemctl restart -v` is the best!
Y’all… #Pinchflat is awesome! #Linux Unplugged had mentioned it many times, but it’s so much nicer than I realized. As a bonus, integrating the containerized version with #Jellyfin that comes from #nixpkgs was pretty straightforward: https://github.com/genebean/dots/pull/572
[ #FOSS #NixOS ]
I added (begin ...) to the syntax of entries in nix-set and nix-setrec of Pipchix.
This way you can group entries within single s-expressions. It is potentially useful with advanced macro and file inclusion systems. And it is harmless. ‘begin’ is already a keyword.
I am not myself making much use of it yet. But for instance if you could build code from quoted s-expressions. You can do that with advanced macro systems.
Actually you can do that with (eval ...) in a standard Scheme.
Without Haskell:
Searching 328,704 packages.
With Haskell:
Searching 1,556,407 packages.
@karolherbst I see several packages on nixpkgs (#NixOS) doing that, yes
It's time to scratch that itch again.
I've got a bit bored of my #debian + #ansible setup. On the older servers it's a little slow and prone to breakage. Playbooks can easily break due to small changes. So it feels like I'm always fiddling to keep them working.
I'm curious what #nixOS is like. The "write your config once, keeps working" seems very tempting.
On the other hand, switching to #pyinfra and/or #alpine may also scratch that itch.
But first, upgrade to #debian #trixie (well #armbian)
