turning my #nixos config into a #flake and now i gotta name device specific configs so now i have to think of a system to name my devices (2 desktops, 3 laptops, 1 server, 2 sbcs) after.
so far i thought of #tf2 classes (tho that limits the amounts of devices in the future very much (then again, naming my main pc saxton hale would also be dope)), #ltd2 units or, being the basic bish i am, rocket ships.
anyone got a good system i could use?
Made a transparent network bridge on #NixOS which sits between router & #LAN switch, monitoring traffic for #IDS #intrusiondetection , #Suricata and #Zeek capture and analyze packets → #Filebeat ships #logs → #Elasticsearch with #GeoIP ingest pipeline → #Grafana setup of dashboard to visualise data is defined in flake itself so using the flake will give the same dashboard. #flake details here https://codeberg.org/adingbatponder/reticulum_nixos_flake/src/branch/main/features/network-appliance
Hardware: HP EliteDesk 800 G1 SFF 16Gb RAM & https://www.jacob.de/produkte/Intel-Ethernet-Server-Adapter-I350-T4-I350T4V2-artnr-2094756.html #i350t4
I made a program for #Steam on #Linux that creates a by-name folder for the compatdata folders of steam games. Basically instead of looking up what a game's AppID is, you can go to compatdata/by-name/My Summer Car/ instead!
https://github.com/Krutonium/SteamByName
Oh and it has a #Flake for #Nix and #NixOS users.
#MIT License. #Linuxgaming to cover all my bases.
#PR 's Welcome!
@BrideOfLinux #nixos #flake #flakes #claude #claudecode
in flake.nix
claude = pkgs.mkShell {
buildInputs = with pkgs; [
nodejs_24
nodejs_24.pkgs.npm
];
shellHook = ''
# Install claude-code if not already installed
if ! command -v claude-code &> /dev/null; then
echo "📦 Installing claude-code..."
npm install -g @anthropic-ai/claude-code
fi
'';
};
then: nix develop .#claude
from the flake directory
then: claude
I just came across this #nix #flake for a personal project in #scala: https://github.com/7mind/squish-find-the-brains
No more vendoring sha to update, and be lockfile oriented. It worked in just 2 minutes for my multi module / multi main project. It's a really nice way to build/distribute my app to my server!
and now I reveal the secret third thing I use to build my system: unflake
unflake is a tool that allows you to stop writing .inputs.foo.inputs.nixpkgs.follows all the time while deduplicating your dependencies. it also frees you from other flake idiosyncrasies like requiring flake.nix to be committed to the repo or copying the whole directory into the store.
README has more details and you can ask me questions about it here or in a discourse thread
(or direct codeberg link: https://codeberg.org/goldstein/unflake)
@xameer I am running from scratch builds of my #flake over and over again on top of a fresh a vanilla #nixOS install with normal internet speeds, to test my #cores hardware requirements. It has not been a problem of more than about 60 mins on 1 core 2.1 GHz machine, 30 mins on 2 core .... best being 8 core at 15 mins with zero time saving for > 8 core use. What does your build have ?
Problem was flakeRoot = "${inputs.self}" in #rust #derivation in flake caused the rust code to swallow whole flake anew for any flake file change, even changes completely unrelated to the rust code, meaning a whole rebuild. Changed that to a find_flake_dir() function that discovers flake directory by walking up if FLAKE_DIR environment variable is not set.
Took time down from always 22 mins, to 2 mins 20 sec for a minor nix fix rebuild. Ta #Claudeai #buildtime #buildtimes #nix #nixos
#flake
In a #nixos #build and #switch of a #flake, my entire #rust #derivation ( which is just a program in the flake ) gets built meaning that it takes eons: even if the change to the flake that made the build necessary was a trivial change to a thing that has no interaction with the rust derivation. What am I doing wrong? Thanks for any pointers... #flakes #buildtime #buildtimes
@fzer0 Flake sagt er sei seitdem viel ruhiger. Und er vertippt sich auch nicht häufiger auf seinem Keyboard...
#rammstein #flake #treadmill
https://youtu.be/bk09OEJ83zw
don’t use “nixos-unstable” folks if you’re not up for it.
This happens roughly on a bi-weekly basis :AngeryCat:
開発を効率化するPython自動整形ツール：`flake8`と`Black`
https://qiita.com/KivoraX/items/452a72fc37b85ff0b6b7?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
Letra da música “Flake” de Jack Johnson
#JackJohnson #Flake
https://daletra.com.br/jack-johnson/letra/flake.html
https://codeberg.org/wyfy/yggdrasil/src/branch/refactor
The repo in question. I'm open to critism, kinda. The first time I opened myself up to it, I got some toxic feedback. But this most recent time I asked, I had a lot of good discourse and learned a lot.
The thought behind all this is to have tons of Norse mythology references, work on multiple platforms, hope it gets forked down the road, maybe some pull requests, a command/script to get this installed and to learn/have fun.
It sucks that I'm so tired, but I can't seem to fall asleep. I know the sooner I fall asleep, the sooner I can work on this flake before classes at college. And the sooner I might have some feedback from people.
Consulta la letra de la canción “Flake” de Jack Johnson
#JackJohnson #Flake
https://daletra.net/jack-johnson/letras/flake.html
@willbush Thanks very much for this info. Indeed in the end one errs on the side of persisting even the stuff one might ideally want to purge on reboot. I am planning using a #nixos #flake arrangement with some #btrfs and #impermanence maintenance scripts but that makes it a bit of a babysitting process. I try to expose all error messages & not ignore them so my flake system is going to be a babysitting process anyway & more checks do not change the basic maintenance routine required. Will see.
@agowa338 @arianvp Well actually claude.ai (pro subscription) has a thing called 'claude code' which can run like on the command line and operate on the command line (without sudo) and is beyond remarkably helpful and insanely efficient for nixOS #flake and config issues in my experience. In fact, it makes #nixOS 100% accessible to total novices and experimenters like me. I was very sceptical but my experience of nixOS setup using #claudecode was .... see image for the right word in French.
#nixos boot error #gnome pop-up using #zenity that warns of boot errors, unless the error has already been classified by you as harmless the last time it appeared in the pop-up,
see #flake #module https://codeberg.org/adingbatponder/reticulum_nixos_flake/src/branch/main/modules/boot-error-notifications.nix
The errors are manually checked with #AI eg Claude before classifying them as irrelevant with a radio button & hiding them henceforth from appearing. If no boot errors, no pop-up. This #nixosaiflakehack was iteratively assisted by #claude . Spot bugs early when #tweakingflakes.
#reticulum #rns in #nixos
A beta #flake that installs (amongst other things) #meshchat #reticulummeshchat and #nomadnet
https://codeberg.org/adingbatponder/reticulum_nixos_flake
#derivation #nixospackages
The flake was hammered out using chatGPT iteratively from a non-AI base flake. #reticulumnetworkstack #reticulumnetwork
See my take on the context and Why NixOS here: https://www.loramesh.org/#nixos
