nixos-servers/README.md

# nixos-servers

Nix definitions to configure our physical servers.
Currently, our three main servers are all Nixified!

## Additional documentation

- [Kubernetes](docs/kubernetes.md)

## Prerequisites

1. Install the Nix package manager or NixOS ([link](https://nixos.org/download))
2. Enable flake and nix commands ([link](https://nixos.wiki/wiki/Flakes#Enable_flakes_permanently_in_NixOS))
3. Install Direnv ([link](https://direnv.net/))
4. Allow direnv for this repository: `direnv allow`

## Bootstrapping

We bootstrap our physical server using [nixos-anywhere](https://github.com/nix-community/nixos-anywhere).
This reformats the hard disk of the server and installs a fresh NixOS.
Additionally, it deploys an age identity, which is later used for decrypting secrets.

⚠️  This will wipe your server completely ⚠️

1. Make sure your have a [Secret service](https://www.gnu.org/software/emacs/manual/html_node/auth/Secret-Service-API.html) running (such as Keepassxc) that provides the age identity.
2. Ensure you have root SSH access to the server.
3. Run nixos-anywhere: `./bootstrap.sh <servername> <hostname>`

## Deployment

To deploy all servers at once: `deploy`
To deploy only one server: `deploy --targets .#<host>`

## Known bugs

When deploying a new virtiofs share, the error `Failed to connect to '<name>.sock': No such file or directory` can occur.
This seems to be a bug in `microvm.nix` and I opened a bug report [here](https://github.com/astro/microvm.nix/issues/200).
A workaround is to deploy the share without `deploy-rs`'s rollback feature enabled:
```
deploy --targets .#lewis --auto-rollback false --magic-rollback false
```
init 2023-11-05 17:43:32 +00:00			`# nixos-servers`

			`Nix definitions to configure our physical servers.`
update readme 2024-01-28 13:14:17 +00:00			`Currently, our three main servers are all Nixified!`
init 2023-11-05 17:43:32 +00:00
restructure documentation 2023-12-29 11:51:42 +00:00			`## Additional documentation`

			`- [Kubernetes](docs/kubernetes.md)`

update readme update boostrap script 2023-11-15 12:24:06 +00:00			`## Prerequisites`
update README change directory naming 2023-11-05 18:03:44 +00:00
update readme update boostrap script 2023-11-15 12:24:06 +00:00			`1. Install the Nix package manager or NixOS ([link](https://nixos.org/download))`
			`2. Enable flake and nix commands ([link](https://nixos.wiki/wiki/Flakes#Enable_flakes_permanently_in_NixOS))`
			`3. Install Direnv ([link](https://direnv.net/))`
			4. Allow direnv for this repository: `direnv allow`
initial nixos-anywhere 2023-11-13 21:44:43 +00:00
update readme update boostrap script 2023-11-15 12:24:06 +00:00			`## Bootstrapping`
initial nixos-anywhere 2023-11-13 21:44:43 +00:00
update readme update boostrap script 2023-11-15 12:24:06 +00:00			`We bootstrap our physical server using [nixos-anywhere](https://github.com/nix-community/nixos-anywhere).`
			`This reformats the hard disk of the server and installs a fresh NixOS.`
			`Additionally, it deploys an age identity, which is later used for decrypting secrets.`
update README change directory naming 2023-11-05 18:03:44 +00:00
update readme update boostrap script 2023-11-15 12:24:06 +00:00			`⚠️ This will wipe your server completely ⚠️`
update README change directory naming 2023-11-05 18:03:44 +00:00
update readme update boostrap script 2023-11-15 12:24:06 +00:00			`1. Make sure your have a [Secret service](https://www.gnu.org/software/emacs/manual/html_node/auth/Secret-Service-API.html) running (such as Keepassxc) that provides the age identity.`
			`2. Ensure you have root SSH access to the server.`
WIP: nixos-anywhere for virtual machines 2023-11-25 20:00:21 +00:00			3. Run nixos-anywhere: `./bootstrap.sh <servername> <hostname>`
Update README.md 2023-11-05 18:07:32 +00:00
update readme update boostrap script 2023-11-15 12:24:06 +00:00			`## Deployment`
Update README.md 2023-11-05 18:07:32 +00:00
restructure documentation 2023-12-29 11:51:42 +00:00			To deploy all servers at once: `deploy`
			To deploy only one server: `deploy --targets .#<host>`
update readme about microvm bug 2024-02-05 21:50:57 +00:00
			`## Known bugs`

			When deploying a new virtiofs share, the error `Failed to connect to '<name>.sock': No such file or directory` can occur.
			This seems to be a bug in `microvm.nix` and I opened a bug report [here](https://github.com/astro/microvm.nix/issues/200).
			A workaround is to deploy the share without `deploy-rs`'s rollback feature enabled:
			```
			`deploy --targets .#lewis --auto-rollback false --magic-rollback false`
			```