Write a very general draft for a default.nix, initial packages, bootloader, networking etc.

Might be invalid eventually based on f-klubben/stregsystemet#407, don't work on this issue until this has been adressed

Having CI through GitHub Actions would allow us to automate quite a few tasks. Initially we could use it to automatically check that packages build, and that their tests run successfully, before we merge PRs.

Later on, after the VPS is up and running, we might also automate deployment, though I think that should be covered by a separate issue where the concrete details of that could be hashed out.

thinking something like this:

dev env

• recommended to test in a VM
  • maybe even add how to replicate the system
• clone to /etc/nixos

new services

• add in /etc/nixos/services
• custom services example

some diagram of the system architecture could also be nice, like where the http server would have endpoints at, or which services are at which ports

Most of the work is done ish, main tasks remaining is:

• dependencies:
  • django-select2
• options
  • settings.py options (sed -i ''<line num> i <option> = <value>" treo/setup.py in reverse order is sufficient, do this for every config option)
  • db file (this has to be set to a writable location)
  • data file (example is the ones under stregsystem/fixtures/)

notes

• django-select2 is not in nixpkgs, so we have to package this ourselves as well