- Kyoto, Japan
- https://pvv.ntnu.no/~oysteikt/
-
ワンワン :3 :3 :3
- Joined on
2023-06-04 -
-
It simplified the logic quite a bit. If we want to be able to toggle worblehat/dibbler separately, we would've needed to make the command added to ExecStart conditionally worblehat or dibbler,…
Sure, that would fix it here at least. Not sure what to do about the leftover modules in the long run, they are kinda useful for testing but might become a pain to maintain.
I don't think the dibbler and worblehat modules are being used anymore, now that all config is made through the drumknotty module. The overlays need to stay though
If it works in the current state, feel free to merge. The comments I left are mostly things that could be fixed later
This is 100% gonna bootloop in the future, should probably be made a priority despite not being necessary.
Using screen windows for now is probably fine, but it would be kinda nice at some point to add a hotkey daemon or something that would let you press a single key to toggle windows. Maybe actkbd? Then we can bind it to a numpad key or something, and add a label on top of the key to press or use the numpad that is (were?) hanging on the wall.
You'll likely want something along the lines of restartTriggers = config.environment.etc."dibbler/dibbler.toml".source here, and for every other unit that should restart whenever the content of that file changes. Same for worblehat
Should probably add some sort of unit here that handles database migrations before startup, can be done in another pr
In my experience, conditional imports (as opposed to conditional config or a conditional enable value) can sometimes be a source of issues when doing more advanced nixos moduling, but I doubt anything is going to happen in this case.