Skip to content
TEGAR-AJA avatar

Blog

What managing 40+ Linux servers taught me

Patterns from enterprise/dedicated server operations: monitoring, failover, automation, and out-of-band hardware.

LinuxInfrastructureOps

At SANAK CYBER I manage 40+ enterprise and dedicated Linux servers. At that scale, snowflake configs die — you need monitoring, runbooks, and automation (Terraform, GitHub Actions, scripts).

Hardware access matters too: Dell iDRAC and HPE iLO let you fix boot and network problems without walking into a data center. Combine that with Prometheus/Grafana and you catch issues before customers do.

The goal isn't more servers — it's infrastructure that's observable, repeatable, and boring in the best way.

Read more

Infrastructure as a product, not a pile of servers

Why Kilat Cloud is built as an abstraction layer — API-driven provisioning instead of manual config.

Troubleshooting across the full stack

App → OS → storage → network → virtualization → hardware → provider. Real incidents rarely respect layer boundaries.

Why I ship static-first when I can

Static HTML is still undefeated for content sites — here's how I decide when to reach for it.

Your GitHub is a portfolio — treat it like one

187 public repos: consistency and good READMEs matter more than any single flashy project.

Accessible by default, not as an audit

Focus states, contrast, and semantics are cheaper to bake in than to retrofit.

Performance budgets that actually stick

Setting a number is easy. Keeping it green takes tooling and culture.

From side project to something people use

The unsexy work: auth, error states, empty states, docs — the gap between demo and product.

← All posts