Name		Name	Last commit message	Last commit date
parent directory ..
12kingdoms-shoukei		12kingdoms-shoukei
darwin-fern		darwin-fern
darwin-harmonica		darwin-harmonica
idols-ai		idols-ai
idols-aquamarine		idols-aquamarine
idols-kana		idols-kana
idols-ruby		idols-ruby
k8s		k8s
README.md		README.md

README.md

Hosts

12kingdoms:
1. shoukei: NixOS on Macbook Pro 2020 Intel i5, 13.3-inch, 16G RAM + 512G SSD.
darwin(macOS)
1. fern: MacBook Pro 2022 13-inch M2 16G, mainly for business.
2. harmonica: MacBook Pro 2020 13-inch i5 16G, for personal use.
k8s: My Kubevirt & Kubernetes Clusters
idols
1. ai: My main computer, with NixOS + I5-13600KF + RTX 4090 GPU, for gaming & daily use.
2. aquamarine: Kubevirt Virtual Machine.
  - Monitoring(prometheus, grafana, exporters), CI/CD(gitea, runner), homepage, file browser, and other services.
3. ruby: Not used now.
4. kana: Not used now.
Other aarch64/riscv64 SBCs: ryan4yin/nixos-config-sbc

How to add a new host

Under hosts/
1. Create a new folder under hosts/ with the name of the new host.
2. Create & add the new host's hardware-configuration.nix to the new folder, and add the new host's configuration.nix to hosts/<name>/default.nix.
3. If the new host need to use home-manager, add its custom config into hosts/<name>/home.nix.
Under outputs/
1. Add a new nix file named outputs/<system-architecture>/src/<name>.nix.
2. Copy the content from one of the existing similar host, and modify it to fit the new host.
  1. Usually, you only need to modify the name and tags fields.
3. [Optional] Add a new unit test file under outputs/<system-architecture>/tests/<name>.nix to test the new host's nix file.
4. [Optional] Add a new integration test file under outputs/<system-architecture>/integration-tests/<name>.nix to test whether the new host's nix config can be built and deployed correctly.
Under vars/networking.nix
1. Add the new host's static IP address.
2. Skip this step if the new host is not in the local network or is a mobile device.

idols - Oshi no Ko

These four servers are named after the four main characters of the mange/anime Oshi no Ko.

rolling girls

My All RISCV64 hosts.

Distributed Building

I usually run the build command on Ai and nix will distribute the build to other NixOS machines, which is convenient and fast.

When building some packages for riscv64 or aarch64, I often have no cache available because of various changes under the hood, so I need to build much more packages than usual, which is one of the reasons why the cluster was originally built, and another reason is distributed building is cool!