File structure

.
├── deimous -> My laptops configuration, will be split into more parts as time goes on, primarily for ssh, which will be gitignore'ed
│  ├── deimous.nix
│  └── hardware-configuration.nix
├── flake.lock
├── flake.nix -> The main mess
├── LICENSE
├── pkgs -> Custom packages not found in the nixpkg repository
│  ├── niri-empty
│  │  └── package.nix
│  ├── oniri
│  │  └── package.nix
│  ├── sff
│  │  └── package.nix
│  └── tinyfetch
│  └── package.nix
└── README.md

Later I will add phobius, the configuration which is for my pc/server and areus, the configuration for my arm laptop.

As will be noticed as this configuration grows, I refuse to split it into many files if I can avoid it, this methodology allows me to A) Easily search certain functions for each device B) Easier overview of everything concering the configuration In my opinion, multi file configurations add a lot of unecessary headache. The configurations is split into to me logical blocks, where at the top lie declerations with some configuration, and at the bottom will always be packages without a configuration, as may be noticed I also order those packages alphabetically, this is just a choice and I should probably order it by use case like

#System utils
btop
iotop

but for now alphabetical works. As of Jun 17th, the configuration primarily focuses on my "experimitation machine" (my laptop) so when it is ready, I can mostly copy the configuration to apply to other devices, which due ot hte nature of being a single file I can easily just apply it to the other devices no fuss. If you look at flake.nix you will notice I do declare some packages and services in it, those are things that apply to all my configurations, such as I always use niri, always have steam, and so on. You may also notice that fish is pretty empty (and unused as of now), that is because I dislike how it looks by default, so I am gonna first configure it then enable. I wll later add the niri-flake, and configure my niri from that, but for that I also have to get my niri configuration to a way I like it.

Sidenote

Currently I am working on my own text editor because I have never liked neovim (which I tolerate right now), helix, nor emacs (and if you notice the patern, I tried gui editors but I prefer tui), ironically I was fine with nano but it was so limiting that I ended up prefering neovim. I am making it in rust to learn rust from the project, and as such it will probably be really jank.

Roadmap

Since this is a rather simple project, its just the configuration of my system, the roadmap is as such, simple. The only goal is to get the configuration to a state where any app installed on the system can be instantly replicated with me just installing the flake, and for me to be able to have it a comfortable state where I can safely run it on my PC and main laptop.

Right now the main goals are:

- Making a configuration for all my apps that looks nice and integrates well with the rest of the system
- Porting my PCs docker containers to nix schema, and some of the apps which I may use to it as well
- Making a flake for alacritty (since using the home manager module is kind off out of the question, due to it not applying the configuration for all users as far as I can tell)
- Possibly making a flake for helix or if I decide helix is not for me, then making my own text editor and the coresponding configuration flake for it.
- Increase security by introducing jail.nix
- Port the flatpaks I use (except flatseal of course) to native nixpkgs
- Commit my custom packages to nixpkgs