#StarWarsOutlaws + #kryschen
🪐 Star Wars Outlaws 🪐
#StarWars #Outlaws #KayVess #Nix #PhotoMode #VirtualPhotography #VPRepost #ThePhotoMode #VPSupport #PS5 #PS5Share #TheCapturedCollective
5
1
0
0
#Nix
Latest posts tagged with #Nix on Bluesky
Posts tagged #Nix
I am starting to understand more and more why people don't merge their stuff into #nixpkgs :akko_scream2:
Like there is a non-0 chance of me just being stupid but wtf is this
github.com/NixOS/nixpkgs/pull/49952...
- posted by Valerie
0
0
1
0
At PlanetNix 2026, Farid talked about how far you can really take #Nix: Going all the way down to kernel-level changes, building things exactly how you want, and trying ideas that would normally feel way too risky.
That’s kind of where the magic is!
0
0
0
0
#StarWarsOutlaws + #kryschen
🪐 Star Wars Outlaws 🪐
#StarWars #Outlaws #KayVess #Nix #PhotoMode #VirtualPhotography #VPRepost #ThePhotoMode #VPSupport #PS5 #PS5Share #TheCapturedCollective
53
6
0
0
#StarWarsOutlaws + #kryschen
🪐 Star Wars Outlaws 🪐
#StarWars #Outlaws #KayVess #Nix #PhotoMode #VirtualPhotography #VPRepost #ThePhotoMode #VPSupport #PS5 #PS5Share #TheCapturedCollective
15
3
0
0
#StarWarsOutlaws + #kryschen
🪐 Star Wars Outlaws 🪐
#StarWars #Outlaws #KayVess #Nix #PhotoMode #VirtualPhotography #VPRepost #ThePhotoMode #VPSupport #PS5 #PS5Share #TheCapturedCollective
13
4
0
0
Reading this book about Nix/NixOS. Seems to be very good!
mhwombat.codeberg.page/nix-book/
#nix #nixos
1
0
0
0
![screenshot of the first page of my “Stamp It! All Programs Must Report Their Version” blog post:
Recently, during a production incident response, I guessed the root cause of an outage correctly within less than an hour (cool!) and submitted a fix just to rule it out, only to then spend many hours fumbling in the dark because we lacked visibility into version numbers and rollouts… 😞
This experience made me think about software versioning again, or more specifically about build info (build versioning, version stamping, however you want to call it) and version reporting. I realized that for the i3 window manager, I had solved this problem well over a decade ago, so it was really unexpected that the problem was decidedly not solved at work.
In this article, I’ll explain how 3 simple steps (Stamp it! Plumb it! Report it!) are sufficient to save you hours of delays and stress during incident response.
[…]](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:eb3563jmh2vjnrlkwujxqdwg/bafkreibmyjp2vprkz3vd4quze4ptlmt5sgz32mjc2bycogzwu6ps2odxpq)
screenshot of the first page of my “Stamp It! All Programs Must Report Their Version” blog post: Recently, during a production incident response, I guessed the root cause of an outage correctly within less than an hour (cool!) and submitted a fix just to rule it out, only to then spend many hours fumbling in the dark because we lacked visibility into version numbers and rollouts… 😞 This experience made me think about software versioning again, or more specifically about build info (build versioning, version stamping, however you want to call it) and version reporting. I realized that for the i3 window manager, I had solved this problem well over a decade ago, so it was really unexpected that the problem was decidedly not solved at work. In this article, I’ll explain how 3 simple steps (Stamp it! Plumb it! Report it!) are sufficient to save you hours of delays and stress during incident response. […]
![screenshot of the last page of my “Stamp It! All Programs Must Report Their Version” blog post:
Conclusion: Stamp it! Plumb it! Report it!
My argument is simple:
Stamping the VCS revision is conceptually easy, but very important!
For example, if the production system from the incident I mentioned had reported its version, we would have saved multiple hours of mitigation time!
Unfortunately, many environments only identify the build output (useful, but orthogonal), but do not plumb the VCS revision (much more useful!), or at least not by default.
Your action plan to fix it is just 3 simple steps:
Stamp it! Include the source VCS revision in your programs.
This is not a new idea: i3 builds include their git-describe(1) revision since 2012!
Plumb it! When building / packaging, ensure the VCS revision does not get lost.
My “VCS rev with NixOS” case study section above illustrates several reasons why the VCS rev could get lost, which paths can work and how to fix the missing plumbing.
Report it! Make your software print its VCS revision on every relevant surface, for example:
[…]](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:eb3563jmh2vjnrlkwujxqdwg/bafkreie44kyf3bi262fe6se54yj26txtvxmx6dwqk6jrtqhum7a7is2gs4)
screenshot of the last page of my “Stamp It! All Programs Must Report Their Version” blog post: Conclusion: Stamp it! Plumb it! Report it! My argument is simple: Stamping the VCS revision is conceptually easy, but very important! For example, if the production system from the incident I mentioned had reported its version, we would have saved multiple hours of mitigation time! Unfortunately, many environments only identify the build output (useful, but orthogonal), but do not plumb the VCS revision (much more useful!), or at least not by default. Your action plan to fix it is just 3 simple steps: Stamp it! Include the source VCS revision in your programs. This is not a new idea: i3 builds include their git-describe(1) revision since 2012! Plumb it! When building / packaging, ensure the VCS revision does not get lost. My “VCS rev with NixOS” case study section above illustrates several reasons why the VCS rev could get lost, which paths can work and how to fix the missing plumbing. Report it! Make your software print its VCS revision on every relevant surface, for example: […]
New blog post 🥳
Stamp It! All Programs Must Report Their Version
In this article, I’ll explain how 3 simple steps (Stamp it! Plumb it! Report it!) are sufficient to save you hours of delays and stress during incident response.
Read more: michael.stapelberg.ch/posts/2026-0...
#nix #golang #linux
11
3
1
0
The NixPKGs contracts implementation has another PR at https://github.com/NixOS/nixpkgs/pull/506343 If this gets merged, it'd be another big (though completely optional) addition to how services can be defined (not only) in #NixOS, after the introduction of modular services in 25.11. No clue if […]
0
0
0
0
When they say #nix kills laptop. 3 years ago i didi a garbage collect and laptop died the week after.
Yesterday I did a garbage collect and today i dropped 0.5L of water on the laptop (hand grip suddently failed).
Laptop is drying, let’s hope. Never GC again.
2
0
0
0
OpenCode TUI configuration support has been added via the 'programs.opencode.tui' option. Since OpenCode v1.2.15, TUI-specific settings like 'theme' and 'keybinds' must be in a separate tui.json file instead of config.json. If you currently have 'theme', 'keybinds', or [1/3]
#NixOS #Nix #HomeManager
2
0
1
0
#StarWarsOutlaws + #kryschen
🪐 Star Wars Outlaws 🪐
#StarWars #Outlaws #KayVess #Nix #PhotoMode #VirtualPhotography #VPRepost #ThePhotoMode #VPSupport #PS5 #PS5Share #TheCapturedCollective
16
4
1
0
It took five and a quarter hours for those wondering; emulated platform builds are sloooooow
Ironically #Nix’s greatest strength (how “easy” it is to do cross compilation) is squandered by the fact that cross builds have totally different hashes (they do have different provenances after all) so […]
1
0
0
0
See how financial services teams use Flox and #Nix to ship #CUDA ML stacks with reproducible environments, atomic rollbacks, and provable software supply chains.
buff.ly/gIbNZrH
1
0
0
0
@vivekanandanks Great, we need more good #nix content out there. Youtube is overrun by AI slop (and it's ridiculously hard on the webapp to ignore such channels). I'm on https://tube.tchncs.de for my videos.
0
0
0
0
✨ #Substack *NEW* Germanic Brook Horses: Magnificent Steeds to Ravenous Shape-Shifting Monsters
▶️ shorturl.at/ogKnp
Brook horses are among to the Germanic Nix (Nyx) or water spirits. Enjoy!
#germanmythology #brookhorses #nix #waterspirits #germanmonsters #kinderschreck #naturespirits
30
22
1
3
#Nix folks: Do you use anything like NixOps, Morph, Colmena, or something along those lines? If so, what's your preference?
2
0
2
0
The `programs.codex.rules` option was added to manage Codex `.rules` files declaratively. Each rule is written under `CODEX_HOME/rules/`, with attribute names mapped to `.rules` filenames automatically. Codex uses these rules for persistent command-prefix decisions [1/2]
#NixOS #Nix #HomeManager
0
0
1
0
✨ #Substack *NEW* Germanic Brook Horses: Magnificent Steeds to Ravenous Shape-Shifting Monsters, with video!
Brook horses belong to the Germanic Nix (Nyx) or water spirits. Enjoy!
#germanmythology #brookhorses #nix #waterspirits #germanmonsters #kinderschreck #naturespirits #germannaturespirits
11
9
0
0
Je te parlerais de #nix un jour ;)
1
0
1
0
`deploy --targets .#cloudsdale .#manehattan .#everfree .#canterlot`
Let's update! It's only 10GiB of downloads :)
#nixos #nix
0
0
1
0
![august @eh23 [0x08] 🏳️⚧️🇲🇰](https://cdn.bsky.app/img/avatar/plain/did:plc:gnt4t3h5577tncgersugqmwq/bafkreif7hzdrpsyoy4uc7s7qvxlntrl37qkxnk3efufgtdhqhiaoowjxuq)
many git commits, some 'gitea runner segfaults?', 'what' or 'what the fuck'
comedic gold in our #nix repo
0
0
0
0
No source maps would leak if Claude Code was written in #Nix
2
0
1
0
The tmuxinator integration in 'programs.tmux.tmuxinator' now supports declaring projects via 'programs.tmux.tmuxinator.projects'. Each project is written to '$HOME/.config/tmuxinator/<name>.yaml'. The tmuxinator package can be customised via [1/2]
#NixOS #Nix #HomeManager
3
0
1
0
nix-direnv is great! For those new to #nix #nixos, you can create a flake file in a repo and define which packages are needed for it specifically (i.e. node). But then you would have to run `nix develop` and wait for downloads every time you enter the directory. With nix-direnv you can create […]
0
0
0
0
A new module is available: `programs.aria2p`. Aria2p is a tui client for aria2c. Note: aria2c must be running with the "enable-rpc" setting.
#NixOS #Nix #HomeManager
3
0
0
0
A new module is available: `programs.macchina` Macchina is a system information frontend with an emphasis on performance.
#NixOS #Nix #HomeManager
2
0
0
0