Closes#76.
Note I had not yet manage to successfully test this.
Manually trying the parameterized NixOps4 I tried using the following
command, tho I had yet to get this to work as well:
```sh
DEPLOYMENT='{"domain": "fediversity.net", "mastodon": {"enable": false},
"pixelfed": {"enable": true}, "peertube": {"enable": false}}' nix
develop --extra-experimental-features "configurable-impure-env"
--command nixops4 apply test
```
(or rather, I used a hardcoded Nix here so as to make it not use Lix.)
So far this had failed for me with:
```
the following units failed:
acme-mastodon.web.garage.fediversity.net.service
...
nixops4 error: Failed to create resource garage-configuration
```
For now, I created yet another deployment. Basically, this seems to tell me that we only ever use:
- one deployment per machine (when we change its configuration)
- one big deployment for all of them (eg. for nixpkgs updates or new contributor)
but that the current split into themes doesn't really work. I can discontinue it in another PR.
`fedi201` is accessible under `fedi201.abundos.eu`. Its configuration lives in `infra/fedi201/default.nix`. This Nix file is a NixOps4 resource module, not a NixOS configuration module; you probably want to add a `nixos.module` field to it where you put your NixOS configuration.
Reviewed-on: Fediversity/Fediversity#183
Reviewed-by: kiara Grouwstra <kiara@procolix.eu>
Co-authored-by: Nicolas “Niols” Jeannerod <nicolas.jeannerod@moduscreate.com>
Co-committed-by: Nicolas “Niols” Jeannerod <nicolas.jeannerod@moduscreate.com>