Community IT tutorials, born from real-world mistakes.
OopsIT is a tutorials site covering Linux, networking, Docker, cloud, DevOps, security, databases, web development, Windows, scripting, and everyday troubleshooting. Posts are aimed at a wide audience — students stepping into I.T., self-taught hobbyists, working developers, and senior engineers who just want a quick refresher.
Every post is framed around something that actually goes wrong in practice — a misconfigured service, a confusing error, a deploy that went sideways — and walks through how to recognize, fix, and avoid repeating it.
OopsIT is published by RDahunan I.T. Services, an independent I.T. services practice based in Cebu, Philippines, founded by Reynard B. Dahunan. The same team runs PinoyNotes PH, ShopLinks PH, and a handful of other small client sites. The technical infrastructure (servers, publishing pipeline, analytics, dashboard) is built and maintained in-house.
We're transparent about this: OopsIT uses an AI-assisted publishing workflow. Topics are drafted with the help of large language models (Gemini 2.5 Flash, with fallback providers), then reviewed before they go live. Code samples, commands, and configuration snippets are checked against the actual tools they describe.
We follow Google's guidance on AI-generated content: the goal is helpful, accurate, originalmaterial — not scaled output for its own sake. If you ever spot an error, an outdated step, or something that doesn't match real behavior, please let us know on GitHub Issues and we'll correct it.
OopsIT is supported by display advertising and, where relevant, affiliate links to tools we actually use. Ads are clearly marked. Affiliate links never change which tool we recommend — they're added only after a tool earns its place in a post on technical merits.
Want to write for OopsIT? Sign up, head to Writing Guidelines, and submit a tutorial. We accept first-hand mistake-and-fix stories from anyone in I.T. — no minimum credentials, just real experience and a willingness to be edited.
The fastest way to reach us is GitHub Issues for site or content problems, or our GitHub profile for general inquiries.