refactor!: remove staging environment

- Hard to setup
- Expensive
- For PXE boot testing, just use a VM with network boot

README.md

@@ -52,7 +52,7 @@ Project status: **Alpha** (see [roadmap](#roadmap) below)
 - [x] CI/CD platform
 - [x] Private container registry
 - [x] Distributed storage
-- [x] Support multiple environments (dev, stag, prod)
+- [x] Support multiple environments (dev, prod)
 - [ ] Monitoring and alerting 🚧
 - [ ] Automated offsite backups 🚧
 - [ ] Single sign-on 🚧

docs/src/deployment/configuration.md

@@ -10,7 +10,6 @@ it's the source of truth for my homelab, so you'll need to folk it to make it yo
 | Environment | Branch   | Recommended setup             |
 | ----------- | -------- | ----------------------------- |
 | Production  | `master` | Real hardware                 |
-| Staging     | `stag`   | Multiple VM with network boot |
 | Development | `dev`    | A single Vagrant VM           |
 
 For example, if you're trying out the dev VM, use the development environment:

metal/inventories/stag.yml

@@ -1,10 +0,0 @@
-metal:
-  children:
-    masters:
-      hosts:
-        stag0: {ansible_host: 192.168.1.50, mac: '08:00:27:57:e5:31', disk: sda, network_interface: enp0s3}
-        stag1: {ansible_host: 192.168.1.51, mac: '08:00:27:4d:a2:9c', disk: sda, network_interface: enp0s3}
-        stag2: {ansible_host: 192.168.1.52, mac: '08:00:27:38:85:26', disk: sda, network_interface: enp0s3}
-    workers:
-      hosts:
-        stag3: {ansible_host: 192.168.1.53, mac: '08:00:27:11:28:b3', disk: sda, network_interface: enp0s3}