this is rae's nixOS config meow

• display manager: SDDM (BUT YUO NEVER SEE IT BLEHHHH)
• window manager: openbox
• status bar: yambar

installation

theoretically:

nix-shell -p git
git clone https://git.sr.ht/~roxwize/.dotfiles
cd .dotfiles/
nixos-install --flake './nixos#[hostname]'

from my experience the process is more involved, but it ultimately boils down to those three commands above (the first command is only for bootstrapping). youll need to make a configuration for your host which involves creating default configurations with nixos-generate-config, copying it to your host's folder in nixos/hosts/[host]/, editing it, and then adding it to flake.nix. after that you should clone the repo inside of /home/rae/ on your filesystem

FOOTNOTE: the r5e option set is importantm,, for Difnerent thigs,. Its individual segments can be found in:

• docker/default.nix - this file imports other files which use the r5e set to provide options for configuring predefined docker containers without needing to write yucky yaml, that dumbfuck piece of shit I HATE that STUPID Yaml (see the subdirectories' default.nix files for configuration options)
• i lied HAHA, that is all the set is used for, ill probably make it more all-encompassing when the need for such a thing actually arises ...

raspberry PI devices

raspberry-pi-nix is used to build PI sd card images. have yur lil sd card on hand (paw) and run in the root of the repository:

nix build './nixos#nixosConfigurations.[hostname].config.system.build.sdImage'

and then Wait................... output will be in result/ NYA!!

ermm???

O.K., just take the image in result/sd-image/[whatever], decompress it with zstd, then run dd if=[decompressed image] of=[sd card device WITHOUT partition number] status=progress

the system will automatically resize the root partition to match the size of the SD card, and from there any changes in post should likely be made over ssh...

nixos-rebuild switch --flake './nixos#[hostname]' --target-host root@[hostname]

ssh isnt automatically setup in a way that lets you do this from the start, you should define it in your host configuration beforehand. near has a decent example of this that you can look over if yu want...

usage

the system should boot into openbox and from there you'll have your statusbar and a lot of keybinds to learn x3

openbox hotkeys

Menus
    A-d
        Main menu
    A-/
        Passwords
    A-? (SA-/)
        Application menu
    A-.
        ssh menu
    A-c
        Client (window) menu

Window actions
    A-Return
        Iconify
    A-Up
        Raise
    A-Down
        Lower
    A-[hjkl]
        Move
    CA-x
        Close
    CA-f
        Fullscreen
    CA-m
        Maximize
    SA-Left
        Switch focus to previous window
    SA-Right
        Switch focus to previous window
    A-Tab
        Cycle focus to windows in all workspaces

Workspace management
    A-Left
        Switch to previous workspace
    A-Right
        Switch to next workspace
    A-[123456]
        Switch to specific workspace

Miscellaneous
    A-F12
        Take screenshot
    CA-Return
        Open terminal (kitty)
    CAS-r
        Restart

or:

Alt+Left click and drag over a window to move it
Alt+Right click and drag over a window to resize it
Ctrl+Right click on titlebar to open its window's menu
Alt+C over a window to do the same thing

Double click titlebar to maximize its window completely
Left click maximize button to maximize completely
Middle click maximize button to maximize vertically
Right click maximize button to maximize horizontally

Right click on desktop to open menu
Alt+Right click over a window to do the same thing
Alt+D to open the application launcher

Alt+Left arrow to go to the previous desktop
Alt+Right arrow to go to the next desktop
Alt+[1-6] to go to a specific desktop
Alt+Shift+Left arrow to go to the previous desktop window
Alt+Shift+Right arrow to go to the next desktop window
Alt+Tab to cycle windows in all desktops

(history)

here is the very first finalized version of this config that was originally tested on a qemu vm. it took 14 hours to set up. after running it on the machine itself and switching over to the configuration in its entirety i realized that it was complete and utter HORSESHIT. making things look nice again took another like four hours.