I use this journal to work through Linux operations, dependable releases, and the fundamentals behind cloud infrastructure.
Relevant experience
- Linux/LAMP web hosting: Apache, PHP-FPM, and MySQL.
- DNS and Google Workspace administration.
- Infrastructure and delivery practice with Ansible, GitLab CI/CD, and Docker.
- BS in Computer Engineering; continuing a path toward cloud and DevOps engineering.
How to read my articles
These notes use AI assistance for drafting and lab development. An author byline identifies editorial ownership, not an independent certification of every environment. Each note states whether it is an explanation or has captured lab evidence.
The current lab series was executed in an isolated AI-assisted Linux workspace. A rerun on my own host is a separate review step, and is not claimed here.
Testing and review policy · Contact Romeo
Published notes
- The first 15 minutes of a Linux incident
- IAM before instances: a better first cloud habit
- Build a pipeline you can actually trust
- Design the recovery before the deployment
- A 404 is a clue. Test before you restart.
- Catch a changed artifact before deployment
- An HTTP 200 can still need a rollback
- Choose a VPS you can actually operate