1
1
mirror of https://github.com/divnix/digga.git synced 2024-12-23 16:11:51 +03:00
digga/examples/devos
Chris Montgomery 68ade1816c
devos: devshell: add required pkgs to scope explicitly
the `with pkgs` statement in `commands` muddies the origin of the
variables used within:

- editors are unable to provide helpful advice about undefined variables
  because `with pkgs` acts as a blanket "anything is possible" signifier
- at a cursory glance, it may not be immediately clear that `system` is
  coming from `pkgs.system`
- `lib` is coming from `pkgs.lib`, but we can use the `lib` module arg.
- some pkgs within `commands` are still referenced with
  `pkgs.<package-name>` unnecessarily
2022-04-24 12:27:27 -04:00
..
hosts devos: add a darwin host + separate os-specific configs 2022-04-24 12:27:23 -04:00
lib tree: move everything into examples/devos 2022-02-23 15:21:28 -08:00
modules devos: add a darwin host + separate os-specific configs 2022-04-24 12:27:23 -04:00
overlays tree: move everything into examples/devos 2022-02-23 15:21:28 -08:00
pkgs tree: move everything into examples/devos 2022-02-23 15:21:28 -08:00
profiles devos: add a darwin host + separate os-specific configs 2022-04-24 12:27:23 -04:00
secrets tree: move everything into examples/devos 2022-02-23 15:21:28 -08:00
shell devos: devshell: add required pkgs to scope explicitly 2022-04-24 12:27:27 -04:00
users devos: add a darwin host + separate os-specific configs 2022-04-24 12:27:23 -04:00
.editorconfig tree: move everything into examples/devos 2022-02-23 15:21:28 -08:00
.envrc tree: move everything into examples/devos 2022-02-23 15:21:28 -08:00
.gitignore tree: move everything into examples/devos 2022-02-23 15:21:28 -08:00
COPYING tree: move everything into examples/devos 2022-02-23 15:21:28 -08:00
default.nix tree: move everything into examples/devos 2022-02-23 15:21:28 -08:00
flake.nix darwin: update mkDeployNodes to account for darwin hosts 2022-04-24 12:27:26 -04:00
README.md Merge devos docs and README into top-level 2022-02-26 12:20:58 -08:00
shell.nix tree: move everything into examples/devos 2022-02-23 15:21:28 -08:00

Nix Configuration

This repository is home to the nix code that builds my systems.

Why Nix?

Nix allows for easy to manage, collaborative, reproducible deployments. This means that once something is setup and configured once, it works forever. If someone else shares their configuration, anyone can make use of it.

This flake is configured with the use of digga.