- Powered by
- WordPress
-
[dedo] 6: How fast is Dedo?
dedo v0.15.0, measured from scratch: an MCP server in three commands, a house rule in five lines, 338 lint rules in 0.32 s, and 12,718 authenticated MCP tool calls a second on one CPU core, 25,339 on two.
-
[dedo] 4: House Rules, Your Rules as Lint
Every organisation has conventions no public standard knows about. dedo lets you write them as CEL checks in rules.yml, share them from one git tag, and see them in the editor.
-
[dedo] 3: Adding dedo to an Existing Service
dedo installs one layer at a time: annotations, lint, generators, runtime. Each layer pays for itself. Audit before you enforce.
-
[dedo] 2: Getting Started: Todo Good and Todo Bad
Two to-do services with the same interface. One follows every rule. One breaks every rule, and its tests show what each mistake costs at runtime.
-
[dedo] 1: Define Once, Deploy Everywhere
One .proto file can carry an API’s contract and its operational rules. A linter can make good architecture the easy path. This is why I built dedo.
-
Why Is It v1 for a Namespace but apps/v1 for a Deployment?
If you’ve written more than a couple of Kubernetes manifests, you’ve probably copy-pasted these lines without thinking too hard about them:
-
Why a thousand containers weigh almost nothing
Docker can run a hundred copies of the same image without storing it a hundred times. The trick is copy-on-write — and once you see the layer stack, it stops feeling like magic.
-
Multi-Tenant ERPNext on a Local Kubernetes Cluster
Running three independent businesses on one homelab K8s deployment — with replicated storage, automated cloud backups, and zero vendor lock-in.