Skip to content

Latest commit

 

History

History
201 lines (188 loc) · 10.5 KB

tasks.md

File metadata and controls

201 lines (188 loc) · 10.5 KB

Tasks

Hosts

Homelab

Amphisbaena

  • [/] Check what the error is in the boot (and shutdown) sequence (Looked to be something about "ACPI" I think, I'll need to record the boot sequence to see what it says)
    • Can look at the error with journalctl -b (journalctl -boot presumably?)
    • It appears to be some energy/power saving and underclocking features.
      • This would make sense with how hot my computer gets when it's plugged in even at low processor levels
  • Look at what hardware specific options need to be set for my laptop
  • [/] Setup battery management (tlp?)

Maintenence

Upgrades

  • Setup keybind for hyprctl kill
  • When playing Worldless on xbox controller extra rumbles play after an intended rumble
    • This probably needs an extra driver to be installed
    • It feels like the rumbles are some kind of testing rumble to see if all the different rumbles are working correctly
  • Convert various package installs to modules
    • obs-studio
    • thunderbird
  • When using Hyprland
    • Automatically spawn and move Obsidian in my vault in a specific desktop
    • Automatically spawn and move Firefox in a desktop
    • Automatically spawn and move Thunderbird in a specific desktop
    • Automatically spawn and move terminal (foot) in a desktop (Should I spawn that in a special desktop so I can pull it up with a keybind?)
    • [-] Theme the icons for waybar workspaces such that they represent these specific meanings
  • Configure user accounts under users.users.${name}.whatever
    • I could go back to the old way of extending the host config with the user config
    • Because then I could generate an option for each user and then only if it is enabled do I add the configuration.nix from the user
    • Create an option for each user
    • If the option is enabled add configuration.nix from that folder to the config
    • Automatically create the user using users.users.${user}
  • Special input support
    • Logitech
      • Mouse
      • Keyboard
    • Steelseries keyboard
    • Razor mouse
    • Stream deck
  • [-] See if I can do anything about specialisations
    • If I'm making a specialisation per DE I could loop over the list of all DEs and create specialisations if more than one is enabled
    • Alternatively I could probably add in my implementation of the specialisation option in my modules system and then integrate that into the Nix specialisation option
    • I could potentially convert the opts input into a sub-option of the config input which could then be overriden by specialisations
      • I.e. config.opts=opts; and then overriding it in specialisations config.opts.environment.gnome.enable=lib.mkForce true;
      • Which desktop environment is enabled could be converted to an enum and enum list, i.e. opts.environment.current="gnome"; and opts.environment.enabled=["gnome" "hyprland"]; and then specialisations could be generated for each option in enabled (current would probably be autogenerated)
    • At the moment, the only thing I would really use specialisations for is desktop environments (/window managers) given that managing this is a role already completed by SDDM/display managers I don't think this is a needed task atm

Security

Package additions