| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Modified options used in disk creation so that consumers of this
module will actually pass disko virtual machine tests.
The flat dataset structure is changed from the xnet disk module,
mainly since I never really made use of the nesting properly. The only
place nesting matters is really in the persist dataset, and that one
is managed by hand anyway.
Although the changes pass tests and seem fine, they have not been
tested on actual hardware yet since the dataset layout changes are
destructive to any running machines, and cannot be simply reverted,
since they alter the disk.
/var, /root, and extras are now persisted since they do not expect to
be wiped on reboot. I never really had problems with this but would
rather minimize messing with SystemD's expectations regarding /var especially.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Projects are not necessarily all exported by the system flake, and
should freely support other derivations. The new "mod" directory will be
used for most projects, and it can be imported by machine
configurations.
That said, the tooling around flakes is pretty good and will still be
used until the dependency is lessened.
|
| |
|
|
|
|
|
|
|
| |
System configurations in a known good state. Secrets still have to be
integrated, at this point the nixos-anywhere project will likely handle
this to keep the bootstrap completely automatic since it can copy ssh
host keys to the host prior to install/activation. This would work
nicely with the sops secret module, but a good way to manage host keys
for each machine still has to be decided.
|
| |
|
|
|
|
|
| |
With these changes, the xnet module is useable as a system builder. At
this point, it is still undecided whether all configuration will be
generalized into this module, rather than keeping mini-modules local to
the machine they will run on.
|
|
|
Set up the modules of the flake. At this time, the flake is split into
modules and machines. Considering that additional top-level sections --
such as packages and shells -- will also be added, it might make sense
to keep all nix related things in one top-level directory, alongside the
flake.nix file.
This is all under the assumption that later amendments to the project
will introduce other tech, such as terraform.
|
