Day 3: No Light, But I Finally Understood GitHub & Docker (With Garri & Bus Analogy) 😂

-

  Yesterday NEPA took light — 124 views with laptop off! Today light is back, let's gist!

I used to think GitHub & Docker na big grammar. Until I explained it to my neighbor selling akara:1. GitHub = Your Mama's Soup Pot & Note Book

You know how mama writes soup recipe in a book? If soup spoils, she checks the book to remember yesterday's recipe.GitHub is that book for code.I cook code (add pepper). I write inside GitHub book: "Today I added salt" (git commit -m "added salt"). 

If I spoil the soup (code breaks), I open book and go back to yesterday's sweet soup (git revert) That "src refspec main" error? Na because I tried to serve soup without writing recipe first!  No more "my code disappeared" story!2. Docker = Your Cooler of Rice for Delivery

Imagine you cook jollof for a customer in PH. You want to deliver to Lagos and it must still taste same, hot, with same plate, spoon. If you carry pot open for bus, everything spills! Docker is a COOLER (container). You put your jollof (NGold app) + plate + spoon + stew + even table inside ONE cooler, lock it. On your gas (your laptop), it works.On my gas (AWS EC2 Cloud), you open same cooler — same taste!  No "it works on my machine" lie! 

My command: docker run -p 3000:3000 ngold = "Abeg open cooler for table 3000! "That's why NGold now lives on 32.196.145.76:3000 — inside cooler, inside Cloud! 

Lesson: Cloud Computing is just another person's big kitchen (AWS) where you keep your cooler.From 0 to 124 views, no light can stop us!  Next: Putting cooler inside my own shop Sirvickcloud9.online. Have you ever tasted food that changed taste after delivery? That's what Docker fixes! Comment your experience!Live: 32.196.145.76:3000

Full Dairy: sirvick-deployments.blogspot.com 

Illustration: My Mama checking her GitHub recipe book before adding extra pepper — Port Harcourt style! Drawn for Sirvick DevOps Dairy Day 3.

#CloudComputing  #Docker #GitHub #NigeriaTech #SirvickDairy #LearnInPidgin


    Read also: AWS deployment 
 https://sirvick-deployments.blogspot.com/2026/09/i-deployed-netflix-clone-ngold-to-aws.html

Comments

Post a Comment

Popular posts from this blog

How I Fixed GitHub Error: failed to push some refs to github.com in 2026

-
Today I was deploying my Netflix clone project (NGold) to GitHub when I got this frustrating error: ! [rejected] main -> main (fetch first) error: failed to push some refs to 'https://github.com/Sirvickcloud91/netflix-frontend-1.git' If you are seeing this error, don't panic. I fixed it in 2 minutes. Here is how. Why this Error happens. This error means your GitHub repository has files that your local computer does not have. In my case, I added screenshots on GitHub website, but my laptop didn't have those screenshots. GitHub is telling you: "Hey, fetch first before you push!"  My Situation, I was working on: Project: Netflix Clone - NGold Live: 32.196.145.76:3000 Repo: Sirvickcloud91/netflix-frontend-1 Error happened after adding 6 screenshots to GitHub. SOLUTION - 2 Commands Only Open your terminal in VS Code and run: Step 1: Pull with rebase: (git pull origin main --rebase). This will download the missing files from GitHub to your laptop without creating...
Read more

How I Deployed Netflix Clone (NGold) to AWS EC2 - Live at 32.196.145.76:3000 [Docker + Nginx Guide]

-
I finally deployed my Netflix clone project NGold to AWS EC2! After 3 failed attempts with permission errors and Nginx crashing, it's now LIVE at http://32.196.145.76:3000 Here's exactly how I did it for anyone trying to deploy a React frontend to EC2. My Stack  Frontend: React (from my GitHub: Sirvickcloud91/netflix-frontend-1)  Server: AWS EC2 Ubuntu  Tools: Docker, Nginx, Git  Live IP: 32.196.145.76:3000 Step 1: Launch EC2 and Open Port 3000 Most beginners forget Security Group. You must allow inbound rule: Type: Custom TCP Port: 3000 Source: 0.0.0.0/0 If you don't do this, your app will run but you won't see it in browser! Step 2: Clone and Dockerize On your EC2: git clone https://github.com/Sirvickcloud91/netflix-frontend-1.git cd netflix-frontend-1 docker build -t ngold-frontend . docker run -d -p 3000:3000 ngold-frontend Fix Nginx (My Biggest Headache) Nginx kept showing 502 Bad Gateway. The fix: sudo systemctl restart nginx sudo nano /etc/nginx/sites-availab...
Read more

Understanding Linux Environment — The Real Engine Behind My AWS Cloud Deployment

-
Image
After I deployed my Netflix Clone NGold to AWS EC2 on Day 2, I honestly thought the hard part was over. From Port Harcourt, fighting git push errors, to finally seeing my app live on 32.196.145.76:3000, I felt like a Cloud Engineer already. I was wrong. The real DevOps journey started the moment I SSHed into that black terminal screen. AWS EC2 gives you a virtual computer, but Linux is the operating system that powers it. Without understanding the Linux environment, your Cloud deployment will not survive one day in production. Docker, AWS, Kubernetes — all of them run ON Linux. That was my Day 6 lesson. 1. The Linux File System – Where Everything Actually Lives Unlike Windows with C: and D: drives, Linux has a single tree starting from root (/). This confused me at first. Where is my app? Where are logs? I learned: /home/ubuntu is where my NGold code lives, /var/log is where all error logs hide (this saved me when my container crashed), /etc holds all system configs, and /tmp is ...
Read more