Most applications collect logs passively and review them after something goes wrong. I wanted something different: a system that tracks every visitor in real time, surfaces suspicious behavior automatically, and gives an admin the ability to respond immediately without leaving the dashboard. This post covers how I designed and built that system end-to-end inside an existing Laravel application.

I recently investigated a Stripe checkout issue where a failed payment still affected booking and account balances. What looked like a simple payment failure turned out to be a deeper problem in the payment confirmation flow.

I built a secure CI/CD pipeline for AWS ECS/Fargate to replace manual deployments with a faster, safer, and more repeatable release process. This write-up covers how I approached blue/green deployments, IAM design, secrets management, health validation, and rollback planning in a production environment.

I migrated 876 Events from Cloudways to a secure, scalable AWS stack—ALB → ECS/Fargate (Nginx + PHP-FPM) → RDS Proxy → Aurora MySQL—with Secrets Manager, S3 uploads, SES email, SQS workers, and an EventBridge scheduler, all built via the AWS Console.

Managing multiple Joomla websites can be a challenging task, especially when it comes to keeping them up-to-date with the latest security patches and new features. Updating each website individually can be time-consuming and laborious...

Previous Next

I have put together a quick and easy way to change your network interface. We will be using netplan which is the default these days. We will accomplish this by adding the file below and apply the changes.