I Stopped Deploying Manually - Here’s My CI/CD Pipeline with GitHub Actions

How I moved AquaChain from manual deployments to a GitHub Actions pipeline that catches bad changes before they hit production. AquaChain is a production-focused IoT water quality monitoring platform: sensors send readings into AWS, Lambda services process and analyze them, and the frontend gives admins, technicians, and consumers role-based views into device health, alerts, and operations. Where I Started For a long time, my deployment process looked like this: Build locally SSH into the server Restart the app Hope nothing breaks That last step was the real problem. The moment I finally stopped trusting manual deploys was a frontend release that looked fine on my machine but went out with the wrong production environment settings. AquaChain loaded, but API requests started failing immediately. I was SSH'ing into the box, checking logs, rolling back, and trying to remember which local change caused it. The rollback only took a few tense minutes, but a few minutes of visible production