From 01e2fc8a6f780720785e41212fa08e02f435b14e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Nicolas=20=E2=80=9CNiols=E2=80=9D=20Jeannerod?=
<nicolas.jeannerod@moduscreate.com>
Date: Tue, 25 Feb 2025 11:55:29 +0100
Subject: [PATCH] Update documentation accordingly
---
infra/README.md | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/infra/README.md b/infra/README.md
index 25250245..830eabc7 100644
--- a/infra/README.md
+++ b/infra/README.md
@@ -9,12 +9,11 @@ future, I will improve the provisioning script to make this a bit less clunky.
In the far future, NixOps4 will be able to communicate with Proxmox directly and
everything will become much cleaner.
-1. Choose an id and name for your VMs. It is recommended to choose the first
- free id above 100. As for the name, it is recommended to choose `fedi<id>`.
- For instance, `fedi117` with id `117`.
+1. Choose names for your VMs. It is recommended to choose `fediXXX`, with `XXX`
+ above 100. For instance, `fedi117`.
2. Add a basic configuration for the machine. These typically go in
- `infra/<name>/default.nix`. You can look at other `fedi<id>` VMs to find
+ `infra/<name>/default.nix`. You can look at other `fediXXX` VMs to find
inspiration. You probably do not need a `nixos.module` option at this point.
3. Add the machine to a deployment. This takes place in `infra/flake-parts.nix`.