From e58b48221dc01289ac9c3ef3e0adca0a68e17479 Mon Sep 17 00:00:00 2001 From: Pim Kunis Date: Sat, 10 Feb 2024 22:33:41 +0000 Subject: [PATCH] Update docker_swarm/README.md --- docker_swarm/README.md | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) diff --git a/docker_swarm/README.md b/docker_swarm/README.md index 626195f..b16138e 100644 --- a/docker_swarm/README.md +++ b/docker_swarm/README.md @@ -6,4 +6,23 @@ This lack of redundancy in the cluster is deliberate: in case all nodes are down In case of only one manager node, the cluster is always able to restore itself automatically. While the operating system of the VMs is managed by NixOS, cluster creation and the deployment of workloads is done through Ansible. -In my opinion, Ansible is a perfect fit for environments that tend to change a lot (such as a container cluster). \ No newline at end of file +In my opinion, Ansible is a perfect fit for environments that tend to change a lot (such as a container cluster). + +## Stacks + +On top of the Docker Swarm, we host several services deployed as Docker Stacks: + +- [Nextcloud](https://nextcloud.com/) +- [Paperless-ngx](https://github.com/paperless-ngx/paperless-ngx) +- [Syncthing](https://syncthing.net/) +- [Pi-hole](https://pi-hole.net/) +- [Radicale](https://github.com/Kozea/Radicale) +- [FreshRSS](https://www.freshrss.org/) +- [Traefik](https://traefik.io/traefik/) +- [Forgejo](https://forgejo.org/) +- [KitchenOwl](https://kitchenowl.org/) +- [kms](https://hub.docker.com/r/teddysun/kms/) +- [Inbucket](https://inbucket.org/) +- [CyberChef](https://github.com/gchq/CyberChef) +- [HedgeDoc](https://hedgedoc.org/) +- [Swarm Dashboard](https://github.com/mohsenasm/swarm-dashboard) \ No newline at end of file