~/Welcome to byteDocs
Role: Cybersecurity Practitioner
Status: Active Maintenance
This is my personal Knowledge Base & Lab Documentation. It's a centralized repository where I dump configurations, commands, and "aha!" moments so I don't have to rediscover them three months from now when I've completely forgotten how I set up that one specific config.
Why this exists
I started documenting on Medium and GitHub Gists, but I needed a self-contained, version-controlled environment.
- Control: I own the data, the format, and the history. No platform dependencies.
- Accessibility: If I want to show a command snippet to my 14 years old cousin, he don't need a login. It's just Markdown.
- Methodology: I'm building my own standard operating procedure (SOP) for homelab security, automation, and everything I need.
- Efficiency: Instead of re-searching the same
iptablesrules ordocker-composeconfigs, I write them here.
What's in here
A curated collection of production-ready (and lab-tested) configurations:
- 🖥️ Infrastructure
- 🌐 Networking
- 🔒 Security & Hardening
- 💾 Backups & Recovery
- 🤖 Automation & Scripting
- 🛡️ Vulnerability Management
How to use it
- Search: Use
⌘K(or your editor's search) to find specific commands or configs.
👩🏻💻 If you're reading this and you're not me:
Hi! Feel free to learn from my mistakes. There are plenty, but not documented haha. 🩷
Security Disclaimer
This documentation is for educational, learning and personal lab purposes.