Compare commits

..

No commits in common. "84eec7a39990cb0685cb6d88b3b8f90dfbaebffd" and "ce97b624e0db624bfdcb40e335d189ea0b5f2763" have entirely different histories.

3 changed files with 1 additions and 25 deletions

1
.gitignore vendored
View file

@ -1,2 +1 @@
.direnv
result

View file

@ -78,14 +78,5 @@ See [sops-nix](https://github.com/Mic92/sops-nix)
## VM Configuration
Any NixOS VM can be reconfigured remotely by calling:
**TODO**
```bash
./switch_remote.sh <action> <machine>`
```
- `<action>` can be any of the [standard nixos-rebuild actions](https://wiki.nixos.org/wiki/Nixos-rebuild), e.g. `boot`, `switch`, etc.
- `<macine>` should be the FQDN of the machine config to apply.
The script uses this argument to know how to reach the machine in addition to choosing a nixos configuration from this flake as system source (see [systems/](./systems/)).
This also means that you should have a config entry in you SSH config resolving the system name to an IP address (during the event, we will probably have an internal DNS server which also resolves the hostname).

View file

@ -1,14 +0,0 @@
#/usr/bin/env bash
# a small script for calling nixos-rebuild switch on a remote host but with less repitition
set -euo pipefail
ACTION=$1
HOST=$2
exec nixos-rebuild $ACTION \
--use-substitutes \
--no-build-nix \
--use-remote-sudo \
--build-host "$HOST" \
--target-host "$HOST" \
--flake ".#$HOST" \