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
Topic rooms
| 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.
Rooms for supporters
A voluntary contribution through Ko-fi opens a few extra rooms. It is entirely optional, pay what you want, and it changes nothing to the technical rooms, which stay open to everyone. The Ko-fi bot tags the account automatically; if it fails, a direct message sorts it out by hand.
More on why that support matters on the supporting the site page.
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.