Hi, I'm Alex — an aspiring DevOps / Cloud engineer learning how modern infrastructure works, one deployment at a time.
I'm on a hands-on path from hobby servers to production-grade DevOps. Everything here reflects real projects I deploy and operate myself.
I started with a single VPS and curiosity about "how does the internet actually work?". That turned into self-hosting, reverse proxies, containers and finally a structured DevOps learning roadmap — Linux, Git, Docker, CI/CD, IaC and cloud basics.
Automation over manual work, reproducibility over magic, and clean observability. I build small, testable infrastructure and write down everything I learn so others can follow the same path.
The fundamentals every junior DevOps should feel at home with.
Systemd, permissions, networking & troubleshooting on Debian/Ubuntu.
Images, containers, volumes, networks and Docker Compose workflows.
Branching, pull requests, hooks and clean collaboration workflows.
GitHub Actions pipelines with linting, testing and automated deploys.
Infrastructure as Code for cloud resources, state & modules.
Pods, deployments, services and simple cluster administration.
Reverse proxying, TLS certificates, rate limits and performance tuning.
Scripts that automate the boring parts and fail loudly.
Real, sourced facts about why DevOps and this stack matter.
High-performing DevOps teams deploy more frequently than low performers, with 106× faster lead time and 2,604× faster recovery.
source: DORA / AccelerateChange failure rate is up to 7× lower in high performers — strong testing and CI are the reason.
source: Google Cloud DEI 2023Of engineers' time is spent on maintenance, collaboration and toil rather than new features — automation attacks this directly.
source: Developer ForecastAverage cost reduction from implementing cloud-native and containerised deployments on a single VPS.
source: cloud economics reportsIt took me (I timed it) to go from an edited config to a live deploy using this exact GitHub Actions + push workflow.
prove it: CI cheatsheetDeployments a single immutable image can serve across environments — build once, run anywhere (Docker & K8s principle).
source: 12-FactorFrequently used commands, copy-paste ready. Sources & docs linked at the bottom.
Bashtree -L 2 /pathdu -sh * | sort -hgrep -rn "pattern" .!!find . -name "*.log" -type fdf -hDockerdocker ps -adocker exec -it <ctr> bashdocker build -t my-app .docker compose up -ddocker logs -f <ctr>docker system prune -afGitgit checkout -b feature/xgit reset --soft HEAD~1git diff HEADgit rebase -i HEAD~3git stashgit reflogLinuxss -tulpnsystemctl status <svc>journalctl -u <svc> -ffree -hpkill -f "pattern"find / -xdev -size +500M -exec ls -lh {} \;Kuberneteskubectl get nodeskubectl get all -n defaultkubectl describe pod <name>kubectl logs -f <pod>kubectl exec -it <pod> -- shkubectl port-forward <pod> 8080:80Terraformterraform initterraform planterraform applyterraform fmtterraform validateterraform state listA curated, beginner-friendly library — docs, playgrounds and communities that helped me get from zero to deploying.
Simple steps and the best free resources that worked for me.
Ship and connect applications.
Make it repeatable and scalable.
A daily dose of jokes, memes and a (fake, for fun) live comment board from around the world.
Open to junior roles, internships and interesting side projects. My inbox is always open — I usually reply within a day.