Many many people have complained about the misleading documentation.
Rather than continuing the path of "we need to fix this", we can reduce
the harmful effects of the inaccurate docs by removing them all
together.
Since much of the confusion in the "getting started" docs came from
`bud`-specific instructions, and `bud` is being removed, removing the
inaccurate docs also seems like it can be a kick towards replacing them.
Also:
- The NixOS manual is the canonical guide to installation. We don't need
to repeat its instructions.
- The numerous references to networking configuration don't have a place
within Digga -- I'm assuming these are `bud`-specific things which are
no longer relevant with `bud` gone.
This has been planned for some time.
It seems necessary to do so now because after updating inputs to track
NixOS 22.05 channels and releases, checks fail unexpectedly, with the
traces leading back to `bud`. Disabling its modules allows checks to
run successfully.
Rather than figuring out what's going wrong with `bud`, it seems more
appropriate to remove it as planned.
now that we have per-host custom tests, it does not make sense anymore
to have magic lumpsum tests.
users are encouraged to use the new digga.lib.allProfilesTest standard
test and add it to a host's test like so:
`nixos.<host>.tests = [ digga.lib.allPrefilesTest ];`
this allow users to specifiy per hosts tests in the host api container
under `.test`.
test must be an attrs or a function that is invoked as a package and
that returns an attrs which can be consumed by nixos' `mkTest`.
tests must have a name, so that they can be told apart in the
flake's check attribue.
When following the getting started guide commands were failing due to
the mater branch not existing. I went through and updated all
references in the docs and other scripts from master to main.
As mentioned in #370 it would not result in a directory called `bud`, as
can be seen in the custom `get.bash` command where the directory name
defaults to `devos`.
