Reading a guide answers the question it was written for. It does not answer yours, the one about your cluster, your pipeline, your error message. That is what the Discord server is for.
Why a chat rather than comments
Blog comments are asynchronous, public forever, and nobody comes back to read them. A chat server works the other way round:
- Immediacy: you are stuck on a
terraform plan, you paste the error, and someone answers while you are still making coffee. - Screen sharing: pair debugging becomes a click rather than a scheduled meeting.
- Separate rooms: a Kubernetes question does not drown in a thread about Ansible.
What is inside
The server has two spaces: topic rooms and early access to the guide drafts. Every room is open to everyone: supporting the site does not unlock any extra room.
Topic rooms
Each room covers a tool or a practice, so that the answer to your question is easy to find again for the person who asks it after you. The topics below are the ones that come back most often.
| Room | What gets discussed |
|---|---|
| #terraform | Error logs, home-made modules, cloudinit, state backends |
| #kubernetes | Helm against Kustomize, Ingress, OPA Gatekeeper |
| #ansible | Roles, Molecule, AWX, ansible-lint |
| #gitops | Chart layering, multi-tenant repositories |
Early access to the guides
The published guides are the finished version. On Discord you get the draft: the diagrams, the code snippets, the TODO items still in red. You can ask your questions before a guide is finalised, and it gets corrected as we go. In practice, readers there end up shaping the guide.
The rules
Six rules, and the reason behind each one:
| Rule | Why |
|---|---|
| No mockery, no toxic sarcasm | People learn better without fear of looking stupid |
| Post in the right room | It saves time for whoever searches later |
| Mask IPs and customer names | It protects your employer, and mine |
| No spam, no selling, no affiliate links | The server stays technical |
| Say whether it worked | An answer with a confirmed outcome becomes a shared resource |
| Ping a moderator on a dispute | Handled in the open rather than in private messages |
Moderation escalates in order, and without exception: a warning, then a cool-down, then a ban.
Joining
The server is free and open:
Come in, say hello in the introductions room, and ask your question. Nobody is expected to introduce themselves with a CV.
Supporting the site is a separate gesture: it gives access to no reserved room, and the supporting the site page explains what it pays for: the hosting, the homelab hardware and the time spent maintaining the guides.