Skip to content
Snippets Groups Projects
Select Git revision
  • 1e0c5ba560853a130e5d17c2db3bcd7114d6d5a8
  • develop default protected
  • production protected
  • nixpkgs-upgrade-2025-06-16
  • nixpkgs-upgrade-2024-12-23
  • 190-our-regular-updates-fill-up-the-servers-boot-partitions
  • nixpkgs-upgrade-2024-10-14
  • hro-cloud protected
  • 162.flexible-grafana-module
  • nixpkgs-upgrade-2024-05-13
  • nixpkgs-upgrade-2024-04-22
  • nixpkgs-upgrade-2024-03-25
  • nixpkgs-upgrade-2024-03-18
  • nixpkgs-upgrade-2024-03-11
  • nixpkgs-upgrade-2024-03-04
  • 163.jp-to-ben-for-prod
  • nixpkgs-upgrade-2024-02-26
  • 164.grafana-alert-rules
  • 157.authorize-new-hro-key
  • nixpkgs-upgrade-2024-02-19
  • nixpkgs-upgrade-2024-02-12
21 results

modules

  • Clone with SSH
  • Clone with HTTPS
  • Florian Sesser's avatar
    Florian Sesser authored
    This comes from nixpgks commit 81291cc793cf88bd6eff3fd8512e5eb9d037066c
    and will be included with nixos 22.11.
    1e0c5ba5
    History

    These are mostly modelled on upstream nixos modules. They are generally fairly configurable (they don't tend to hard-code paths, they can be enabled or disabled). They don't know anything about morph (e.g. deployment.secrets) or how the different grids are configured (e.g. grid.publicKeyPath). Each module here tends to define one service (or group of related services) or feature. Eventually, all of these will be imported automatically and controlled by services.private-storage.*.enabled options.