Update readme

README.md

@@ -5,12 +5,14 @@ We use [Kubenix](https://kubenix.org/) to write Kubernetes deployments in Nix!
 ## Images used
 
 Legend:
-- ✨: Image built with Nix (including [NixNG](https://github.com/nix-community/NixNG))
+
+- ✨: Image built with Nix (including
+  [NixNG](https://github.com/nix-community/NixNG))
 - ✅: Official image or trusted publisher
 - 🫤: Unofficial image
 
 | Status | Image                                          | Comments                                                  |
-| ---    | ---   | ---     |
+| ------ | ---------------------------------------------- | --------------------------------------------------------- |
 | ✨     | `nixng-blog`                                   |                                                           |
 | ✨     | `nixng-dnsmasq`                                |                                                           |
 | ✨     | `nixng-attic`                                  |                                                           |
@@ -21,8 +23,9 @@ Legend:
 | ✨     | `nixng-sonarr`                                 |                                                           |
 | ✨     | `nixng-bazarr`                                 |                                                           |
 | ✨     | `nixng-prowlarr`                               |                                                           |
+| ✨     | `nixng-deluge`                                 |                                                           |
+| ✨     | `nixng-mealie`                                 |                                                           |
 | ✅     | `jellyfin/jellyfin`                            |                                                           |
-| ✅ | `linuxserver/deluge` | |
 | ✅     | `ghcr.io/atuinsh/atuin`                        |                                                           |
 | ✅     | `postgres:14`                                  | Database for Atuin                                        |
 | ✅     | `ghcr.io/paperless-ngx/paperless-ngx`          |                                                           |
@@ -47,32 +50,39 @@ Legend:
 
 ## Acknowledgements
 
-- [dns.nix](https://github.com/kirelagin/dns.nix): A Nix DSL for defining DNS zones
+- [dns.nix](https://github.com/kirelagin/dns.nix): A Nix DSL for defining DNS
-- [flake-utils](https://github.com/numtide/flake-utils): Handy utilities to develop Nix flakes
+  zones
-- [kubenix](https://kubenix.org/): Declare and deploy Kubernetes resources using Nix
+- [flake-utils](https://github.com/numtide/flake-utils): Handy utilities to
+  develop Nix flakes
+- [kubenix](https://kubenix.org/): Declare and deploy Kubernetes resources using
+  Nix
 - [nixhelm](https://github.com/farcaller/nixhelm): Nix-digestible Helm charts
 - [sops-nix](https://github.com/Mic92/sops-nix): Sops secret management for Nix
 
 ## Prerequisites
 
-To deploy to the Kubernetes cluster, first make sure you have an admin account on the cluster.
+To deploy to the Kubernetes cluster, first make sure you have an admin account
-You can generate this using `nix run '.#gen-k3s-cert' <username> <servername> ~/.kube`, assuming you have SSH access to the master node.
+on the cluster. You can generate this using
-This puts a private key, signed certificate and a kubeconfig in the kubeconfig directory
+`nix run '.#gen-k3s-cert' <username> <servername> ~/.kube`, assuming you have
+SSH access to the master node. This puts a private key, signed certificate and a
+kubeconfig in the kubeconfig directory
 
 ## Bootstrapping
 
-We are now ready to deploy to the Kubernetes cluster.
+We are now ready to deploy to the Kubernetes cluster. Deployments are done
-Deployments are done through an experimental Kubernetes feature called [ApplySets](https://kubernetes.io/docs/tasks/manage-kubernetes-objects/declarative-config/#how-to-delete-objects).
+through an experimental Kubernetes feature called
+[ApplySets](https://kubernetes.io/docs/tasks/manage-kubernetes-objects/declarative-config/#how-to-delete-objects).
 Each applyset is responsible for a set number of resources within a namespace.
 
-If the cluster has not been initialized yet, we must bootstrap it first.
+If the cluster has not been initialized yet, we must bootstrap it first. Run
-Run these deployments:
+these deployments:
+
 - `nix run '.#bootstrap-default-deploy'`
 - `nix run '.#bootstrap-kube-system-deploy'`
 
 ## Deployment
 
-Now the cluster has been initialized and we can deploy applications.
+Now the cluster has been initialized and we can deploy applications. To explore
-To explore which applications we can deploy, run `nix flake show`.
+which applications we can deploy, run `nix flake show`. Then, for each
-Then, for each application, run `nix run '.#<application>-deploy'`.
+application, run `nix run '.#<application>-deploy'`. Or, if you're lazy:
-Or, if you're lazy: `nix flake show --json | jq -r '.packages."x86_64-linux"|keys[]' | grep -- -deploy | xargs -I{} nix run ".#{}"`.
+`nix flake show --json | jq -r '.packages."x86_64-linux"|keys[]' | grep -- -deploy | xargs -I{} nix run ".#{}"`.