aboutsummaryrefslogtreecommitdiffstats
path: root/docs/meeting_notes/2023-07-11.md
diff options
context:
space:
mode:
authorGravatar Johannes Christ <[email protected]>2024-04-27 21:21:51 +0200
committerGravatar Joe Banks <[email protected]>2024-04-27 21:21:04 +0100
commitde9307796340070c0b44e6325a902184ad65492a (patch)
treef7a873d1a4b14281580b0450ba77ee9290b22c3c /docs/meeting_notes/2023-07-11.md
parentUse same indent for all fail2ban options (diff)
Move documentation to Hugo
Shortly before merge, the repository settings need to be updated to set GitHub Actions as the deployment source, to prevent GitHub from trying to build with Jekyll.
Diffstat (limited to 'docs/meeting_notes/2023-07-11.md')
-rw-r--r--docs/meeting_notes/2023-07-11.md41
1 files changed, 0 insertions, 41 deletions
diff --git a/docs/meeting_notes/2023-07-11.md b/docs/meeting_notes/2023-07-11.md
deleted file mode 100644
index bd9b198..0000000
--- a/docs/meeting_notes/2023-07-11.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-layout: default
-title: "2023-07-11: Devops Meeting"
-parent: Meeting notes
-nav_order:
----
-
-# DevOps Meeting Notes
-
-## Participants
-
-- Chris, Johannes, Bella, Bradley
-
-## Agenda
-
-### New Ansible setup
-
-Chris presented the new Ansible setup he's been working on. We plan to use
-WireGuard for networking. We agreed that selfhosting Kubernetes is not the way
-to go. In general, the main benefit from switching away to Linode to Netcup is
-going to be a ton more resources from the Netcup root servers we were given. The
-original issue with Linode's AKS of constantly having problems with volumes has
-not been present for a while. Chris mentions the one remaining issue is that
-we're at half our memory capacity just at idle.
-
-It's our decision where to go from here - we can stick to the Kubernetes setup
-or decide on migrating to the Ansible setup. But we have bare metal access to
-the Netcup hosts, which makes e.g. managing databases a lot easier. Chris
-mentions the possibility to only use Netcup for our persistence and Linode AKS
-for anything else, but this has the issue of us relying on two sponsors for our
-infrastructure instead of one.
-
-PostgreSQL was set up to run on ``lovelace``.
-
-### Decision
-
-**It was decided to hold a vote on the core development channel, which will be
-evaluated next week to see how to proceed with the setup**.
-
-
-<!-- vim: set textwidth=80 sw=2 ts=2: -->