Contact Us

Contact me


Have a question, suggestion, or you want collaborate?

 I reply within 24 hours.

 Email: ukovick25@gmail.com

 Location: Port Harcourt, Rivers State, Nigeria

Blog: https://sirvick-deployments.blogspot.com

 GitHub: https://github.com/Sirvickcloud91

Whether you are stuck on a GitHub error "failed to push some refs" or you want to know how I deployed NGold on AWS EC2 with Docker + Nginx, feel free to message me. I will explain in  beginner terms

Thank you for reading my diary!



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