yadunut/yadunut.dev
1
0
Fork 0
Code Issues Pull Requests Actions Projects Releases Wiki Activity

Cleaning up nix
All checks were successful
Build OCI Image / docker (push) Successful in 40s
Details

Browse Source
This commit is contained in:
Yadunand Prem 2025-08-14 15:28:25 +08:00
parent e6b7654fe0
commit f1d2e36852
1 changed files with 14 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
content/microblog/2025.smd
View File

@ -12,12 +12,23 @@ A place for short form thoughts and ideas
> This page lists entries for the current year, for past entries consult the [microblog archive](/microblog/).
## [Cleaning up nix]($section.id("2025-08-19T15:31+08:00"))
In the spirit of procastinating on my hard projects, I decided to clean up my nix files, and have some organization in the chaos. The current configuration can be found [here](https://git.yadunut.dev/yadunut/nix), old configuration [here](https://git.yadunut.dev/yadunut/dotfiles)
I didn't think I needed [flake-parts](https://flake.parts/) as I wasn't really writing a lot of modules(? I believe?), but wanted a cleaner way of organizing the files. I found [snowfall lib](https://snowfall.org/) and I've just made the switch to that.
Snowfall is quite interesting, basically providing a opinionated structure to organizing your nix files. The best part is that it auto imports all modules you've defined in the modules folder to both home-manager and NixOS, so that makes the configuration a bit more "magicky" but simpler.
I used to not appreciate magic, cause it made tracing code harder (Didn't really enjoy my foray into Ruby on Rails in 2017), and you had entire IDEs to making that experience better. Nix, being more of a configuration languge, I'm okay with the tradeoffs of magic for simpler configs.
At the same time, I think it'll be easy to migrate off snowfall, I'm not using any of snowfall's more complex features, and will just need a function to auto inject the imports into every home manager and nixOS configuration.
## [Pheonix from the ashes]($section.id("2025-08-12T16:03:58+08:00"))
After yesterday morning's snafu, I gave up on the project and decided to just bring it to a shop to fix. Just for posterity's sake, I decided to try to boot the computer again and IT WORKED? My partner aptly put it as "the load bearing dust accumulated (back in the case)" so now I'm off to finishing the build.
After yesterday morning's snafu, I gave up on the project and decided to just bring it to a shop to fix. Just for posterity's sake, I decided to try to boot the computer again and IT WORKED? My friend aptly put it as "the load bearing dust accumulated (back in the case)" so now I'm off to finishing the build.
Also I've somehow managed to kill an Intel DC S3500 SSD, so now I'm running all of my SSds in RAID 1 or higher levels.
Also I've somehow managed to kill an Intel DC S3500 SSD, so now I'm running all of my SSDs in RAID 1 or higher levels.
I should think of renaming my PC from falcon pheonix...
I should think of renaming my PC from falcon to pheonix...
## [Dead thing dies again]($section.id("2025-08-11T12:00:06+08:00"))
So... I built the computer, put it back into its case, and for a sanity test, I tried booting it up and... it went into the BIOS once, and then crashed and it didn't boot after that...