No description
- Nix 100%
A TLSA record hashes the public key, and lego makes a new key at every renewal by default, so a published record would stop matching after about 60 days and DANE-checking servers would silently refuse delivery. |
||
|---|---|---|
| certs | ||
| devices/balthasar | ||
| modules | ||
| tests | ||
| .gitignore | ||
| flake.lock | ||
| flake.nix | ||
| README.md | ||
| systems.nix | ||
Lilith Semi - Systems
Infrastructure and systems for Lilith Semiconductor
Devices
Balthasar
EDIS Global US East box
- Public entrypoint
Melchior
Switzerland on-prem box
Casper
Souther California on-prem box
Services
Public
git.lilithsemi.com, Forgejo, git over ssh + http(s)mail.lilithsemi.com: mail, no frontent
Private
auth.magi.lilithsemi.com: SSO authenticationgrafana.magi.lilithsemi.com: Grafana dashboardchat.magi.lilithsemi.com: Mattermostmail.magi.lilithsemi.com: Roundcube mail frontendpass.magi.lilithsemi.com: Vaultwardenvault.magi.lilithsemi.com: OpenBaomeet.magi.lilithsemi.com: Lasuite Meetledger.magi.lilithsemi.com: Hledger
Layout
| Path | Holds |
|---|---|
flake.nix |
Inputs, system helpers, treefmt, devshell |
systems.nix |
The host table |
modules/ |
Shared modules. default.nix imports all of them |
devices/<host>/ |
One host. default.nix imports the rest, README.md is its runbook |
certs/ |
Public certificates only. Never a private key |
tests/ |
NixOS VM tests, wired into nix flake check |
A shared module with something to select gives an option under magi.*. A
device turns on what it uses.
Working on it
nix develop
nix fmt
nix flake check
balthasar builds its own system, over SSH, not the workstation. See step 12 of
devices/balthasar/README.md for the full reason and the command. deploy-rs is
wired into the flake (self.deploy.nodes.balthasar) for the day an x86_64
builder exists on the network. It builds locally, so it cannot deploy
balthasar yet. Do not use it.