meowix

This is a project that I am trying to build from scratch¹,
And do not take from other NixOS configurations

Oh well rules didn't work for me!

This is a NixOS configuration that is used for 3 hosts that are all on one PC.
I am treating myself as completely new to NixOS and I will learn making config
Arch Linux tends to break and I need to re-install it everytime
I know there are various tools to install such distro but...
configuring it will be a mess ( and boring )
While on NixOS it is easy by just adding a configuration.

Note about pattern

This is a semi-monorepo style configuration, however I still copied some dendritic pattern practices because I don't have much time to play with my configuration and think philosophically to implement per-program package export and install it inside configuration

For nerds that explode on home-manager If it exists use it, if it doesn't work Get a workaround, if no workaround THEN solution

Map of planned hosts to build

Name	Type	Use case
Meowscarada	NixOS-WSL	Development and Environment
Lucario	NixOS	Gaming, daily drive, Development
Necrozma	nix-darwin	Development and Environment, Apps

More can be seen hosts

Note taking

I will use Obsidian for note taking and it is inside notes directory
I will mostly take notes of strange words, topics, systems, etc. By doing this it will help me get into my project faster
Rather than forgetting what does the code's functions, variables, workarounds do And to make documentation for this project

Rules for this project

AI

• AI Usage for generating/rewriting content is prohibited
• Using AI to fix bugs or grammar/code issues is OK
• Using AI for problem solving suggestions are fine (such as abstract things)
• AI usage should be strict and advanced (like having skills or etc)

Commit messages

For commit messages, use conventional commits
For consistency and readability across versions

The commit message should be structured as it follows:

<type>[optional scope]: <description>
[optional body]
[optional footer(s)]

Formatting

Always format each file if applicable

If applicable is things that are binary files or text, etc

Notes

Take notes using Obsidian and take notes about things that
I do not understand like specific words, (derivations, store path, etc) Code's functions such as resolve, resolveHm, resolveDarwin (lib.mapAttrs', etc)

So just a small wiki for myself that I collected from resources

Layout

Use layout structure that is written in LAYOUT

• The file has tree-structure captured of this project and it's description, It maps the project structure so it will be understandable like what each parts of the project do

---

References

• Host names - Pokédex
• Markdown - Markdown Guide
• Learning Resources - awesome-nix
• Conventional Commits - conventionalcommits.org

Footnotes

1. Except learning resources such as in the the references ↩