#NixOS #Nix #HomeManager
(2/2)
I also plan to explain how this revolutionary system shifts the paradigm for servers and workstations, embedded Linux etc and how it avoids system drift and make things reproducible and reliable
How it's the best distro for developers, DevOps, Platform engineering, IT and Server administration etc
See you all at the event.
🤝Always love to connect with curious and passionate people
#nix #nixos #FOSS #chennai #conference
#chennaifoss #chennaifoss2026
(1/2)
Hi All
I'm happy to announce that I'm a speaker in the Chennai FOSS 2026 conference happening on April 18th 2026
@fossunitedchennai
Title: The era of Declarative Linux via NixOS
My proposal link:
https://fossunited.org/c/chennai/2026/cfp/fjumd5g6qm
I am gonna talk about why NixOS is truly exceptional linux and not yet another distro.
I'll also talk about how it achieves immutability unlike other distros.
How it's way more powerful than tools like ansible, chef, pupper, saltstack etc
#nixos
Alright, so AI Scrapers? I’m sure you’ve heard, they’re kinda awful. Go figure. To give you an idea; I recently had the experience of a couple of scrapers hitting my Forgejo server at the same time. I saw a peak of 33 requests/second, which is just not sustainable on a site like that - They were crawling git history, which is an expensive operation, and was eating up ridiculous volumes of memory, and importantly, CPU time - The i7-6700K in that box was stuck at 100% load for hours before I noticed.
the hardest part of #nixos is deciding when to download the flatpak or when to install the 'native package'.
i assume the native package is the way to go everytime
although, recently i got burned on that assumption for the first time. the obsidian nixos package, seems to be an electron app. so, i just went and installed the flatpak.
trying to install steam nixos package, but it's sooo slow to download. won't build. i might have to just install the flatpak. the internet sucks here at work.
Warning for #NixOS unstable users out there:
I discovered the hard way that if you have the https://github.com/FlameFlag/nixcord flake in your configuration after updating your flakes and rebuild, you'll be unable to properly boot.
The only solution I've found is to disable the Nixcord flake.

When I did last week's update to mfgames-project-setup-flake, I decided to embrace my project layout by having it generate a stub Justfile that would use some wildcard magic to run various formatters and build processes based on the project setup.
For example, if you turn on REUSE (mfgames.project.reuse.enable = true;) for license management, it will add a Just target test-reuse to lint all the files for the REUSE headers and configuration.
But when I went to update mfgames-writing-setup-flake, I wanted to add build-epub, build-docx, and build-pdf options but couldn't because Just doesn't support wildcard items.
So, last night, I got most of the logic to allow me to inject Justfile targets into the generated project. Which means I can:
mfgames.project.just.extraTargets = {
build-epub = {
description="Build the EPUB files.;
group = "development";
text="mfgames-writing build epub";
};
};
And it will generate the stanza properly so just list shows it and just build will automatically call it, all by just including the mfgames-writing-setup-flake into the inputs of your project.
Later, the fedran-writing-setup-flake will extend that even more to include generating files, hooking up themes, and the like so I can easily create a new Fedran project by cp ../allegro/flake.* ../allegro/.envrc .;git add -A .;direnv allow and be up and running.