DEV Community: Miracle Olorunsola

From Zero to Production: My HNG DevOps Stage 0 Journey

Miracle Olorunsola — Mon, 20 Apr 2026 12:00:00 +0000

I just completed a hands-on Linux server setup and deployment no Docker, no automation, just raw DevOps fundamentals.

Here’s exactly how I approached it:

Server Provisioning & Access
Spun up a Linux server on the cloud Connected via SSH using key-based authentication Created a secure non-root user: hngdevops Granted sudo privileges
Security Hardening
Disabled root SSH login Disabled password authentication (keys only) Configured Uncomplicated Firewall: Allowed only ports 22 (SSH), 80 (HTTP), 443 (HTTPS) Blocked everything else
Web Server Setup
Installed and started Nginx

Configured routes:
/ → Static HTML page displaying my HNG username
/api → JSON response:
{
"message": "HNGI14 Stage 1",
"track": "DevOps",
"username": "my-username"
}

SSL Configuration Used Certbot to generate a valid SSL certificate Enabled HTTPS on the server Configured HTTP → HTTPS redirect (301)

5.** Validation & Debugging**

Ensured:
/api returns HTTP 200 with Content-Type: application/json
Username matches exactly (case-sensitive)
SSL is valid (no self-signed certificates)
Firewall and Nginx are active and correctly configured

Key Lessons
Most failures aren’t tools they’re mis-configurations (ports, services, permissions) “Connection refused” vs “Timeout” tells you exactly where the issue is Security first: lock down access before exposing your server


Live Demo

* Deployed and accessible over HTTPS 
This project sharpened my troubleshooting, Linux, and networking skills exactly what real-world DevOps demands.
hashtag#DevOps hashtag#Linux hashtag#Nginx hashtag#CyberSecurity hashtag#Cloud hashtag#LetsEncrypt hashtag#HNG hashtag#TechJourney

HNG Stage 1 DevOps Task Completed — From Infrastructure to API Deployment

Miracle Olorunsola — Mon, 20 Apr 2026 12:00:00 +0000

After successfully setting up a Linux server and configuring Nginx in Stage 0, I took things further in Stage 1 by building and deploying a minimal backend API — focusing not just on development, but on how services run in production.

What I Built
A lightweight API with 3 endpoints:

/ → Confirms the API is running
/health → Health check endpoint
/me → Returns my profile details

All endpoints:
✔ Return JSON (application/json)
✔ Respond with HTTP 200
✔ Optimized for <500ms response time

Deployment Approach

Provisioned a cloud VPS
Ran the app on a non-public port (security best practice)
Configured Nginx as a reverse proxy to handle public traffic
Ensured high availability using a persistent service (systemd)

Key Learning
As a DevOps engineer, deploying isn’t just about infrastructure — it’s about understanding the application lifecycle, performance, and reliability from the inside out.

Live API: http://my-live-domain-or-ip
GitHub Repo: https://github.com/Techgirli

This project strengthened my skills in:

Linux server management
Reverse proxy configuration with Nginx
Service reliability & process management
API structure and performance optimization

On to the next stage

DevOps #HNGInternship #Backend #Nginx #Linux #CloudComputing #APIs

These are some Images from the App.

Miracle Olorunsola — Thu, 09 Apr 2026 12:00:00 +0000

GitHub Repository:

Innovators-UmojaAgri-Org / UmojaAgri-Org

UmojaAgri-Org

UmojaAgri 🌾

AI-Driven Agricultural Logistics Platform

A logistics intelligence platform that helps farmers and transporters monitor produce freshness, predict delivery delays, and reduce post-harvest losses using rule-based AI With the collaboration of the twam we could bring the mobile app to life.

Project Overview

UmojaAgri is an MVP designed to address a major challenge in African agriculture: food spoilage due to unpredictable transportation.

The platform calculates a Freshness Window — a real-time countdown that determines whether produce will arrive at its destination before spoilage risk becomes critical.

It combines logistics tracking, rule-based intelligence, and supply-chain visibility into a single system.

Problem Statement

A significant percentage of agricultural produce in Africa spoils before reaching markets due to:

Poor road conditions
Unpredictable travel times
Lack of real-time freshness tracking
Inefficient logistics coordination

UmojaAgri provides predictive insights so farmers and transporters can make smarter decisions and reduce waste.

Core Features

Produce

…

View on GitHub

Live Demo (Render):
Farmers Dashboard:

umojaagri-org-1.onrender.com

Marketer Dashboard:

umojaagri-org-1.onrender.com

Transporter Dashboard:

umojaagri-org

The Slides on the information UmojaAgri

Miracle Olorunsola — Tue, 07 Apr 2026 12:00:00 +0000

If you’d like to explore UmojaAgri 🌱 in action:
Check out more information

canva.com

You can Explore the app

Miracle Olorunsola — Mon, 06 Apr 2026 13:00:00 +0000

If you’d like to explore UmojaAgri 🌱 in action:
GitHub Repository:

Innovators-UmojaAgri-Org / UmojaAgri-Org

UmojaAgri-Org

UmojaAgri 🌾

AI-Driven Agricultural Logistics Platform

A logistics intelligence platform that helps farmers and transporters monitor produce freshness, predict delivery delays, and reduce post-harvest losses using rule-based AI With the collaboration of the twam we could bring the mobile app to life.

Project Overview

UmojaAgri is an MVP designed to address a major challenge in African agriculture: food spoilage due to unpredictable transportation.

The platform calculates a Freshness Window — a real-time countdown that determines whether produce will arrive at its destination before spoilage risk becomes critical.

It combines logistics tracking, rule-based intelligence, and supply-chain visibility into a single system.

Problem Statement

A significant percentage of agricultural produce in Africa spoils before reaching markets due to:

Poor road conditions
Unpredictable travel times
Lack of real-time freshness tracking
Inefficient logistics coordination

UmojaAgri provides predictive insights so farmers and transporters can make smarter decisions and reduce waste.

Core Features

Produce

…

View on GitHub

Live Demo (Render):
Farmers Dashboard:

umojaagri-org-1.onrender.com

Marketer Dashboard:

umojaagri-org-1.onrender.com

Transporter Dashboard:

umojaagri-org

Project Structure Highlights:
/frontend → Flutter application
/backend → Supabase integration & services
/nginx → Reverse proxy configuration
.github/workflows → CI/CD automation

What this project demonstrates:
Full-stack collaboration (Flutter + Supabase + PostgreSQL)
DevOps pipeline design using GitHub Actions
Cloud deployment and management via Render
Real-world debugging and system optimization

Results:
Faster deployment cycles
Improved reliability through automation
Clean and scalable project structure

Future Improvements:
Container orchestration using Kubernetes
Monitoring & observability with Prometheus + Grafana
Centralized logging and alerting
Scaling into microservices architecture
I’m actively seeking DevOps / Cloud Engineering roles where I can contribute to building scalable, production-ready systems.
Let’s connect
hashtag#DevOpsEngineer hashtag#CloudEngineering hashtag#Kubernetes hashtag#Prometheus hashtag#Grafana hashtag#GitHub hashtag#Portfolio hashtag#OpenToWork
umoja_agri
umojaagri-org-1.onrender.com

Here’s how we structured and deployed UmojaAgri 🌱 from a DevOps perspective. Architecture Overview:

Miracle Olorunsola — Fri, 03 Apr 2026 12:00:00 +0000

Here’s how we structured and deployed UmojaAgri 🌱 from a DevOps perspective.
Architecture Overview:
Flutter (Frontend) → API layer (Supabase) → PostgreSQL database
Nginx acting as a reverse proxy (where applicable)
Application services deployed via Render
CI/CD handled with GitHub Actions

Infrastructure Stack:
Hosting: Render
Backend Services: Supabase
Database: PostgreSQL
CI/CD: GitHub Actions
Containerization: Docker
Server Config: Nginx
CI/CD Workflow:
Code pushed to GitHub
GitHub Actions triggers build & checks
Updates deployed to Render
Backend services sync via Supabase

System Improvements:
Faster and consistent deployments
Simplified rollback via version control
Reduced human error through automation
DevOps Principles Applied:
Automation-first workflows
Service separation (frontend, backend, database)
Scalable and maintainable architecture

Next: GitHub repo + live demo + future upgrades 👇
hashtag#DevOps hashtag#SystemDesign hashtag#Cloud hashtag#Supabase hashtag#PostgreSQL hashtag#Render hashtag#Infrastructure

Back
Dialog content end.
Miracle OlorunsolaStatus is online
MessagingYou are on the messaging overlay. Press enter to open the list of conversations.

Compose message
You are on the messaging overlay. Press enter to open the list of conversations.

Created and Deployed an Agri-Tech

Miracle Olorunsola — Thu, 02 Apr 2026 12:00:00 +0000

I recently joined a team of amazing women to build a mobile app called UmojaAgri Santana Jepchumba Blen Redwan Michelle Fayeun Blessing Omonye Abanonkhua Nkechika Collins Akpe Rotimi Amusa

I deployed UmojaAgri 🌱 an AgriTech platform focused on improving how farmers access tools, insights, and resources.

But beyond development, I approached this project with a DevOps and production-first mindset.

What I implemented:

Containerization using Docker

Automated CI/CD pipelines with GitHub Actions

Reverse proxy configuration using Nginx

Cloud deployment using Render

Debugging real-world deployment issues (including “Cannot GET /”)

Performance & Impact:

Deployment time reduced by ~60% using CI/CD automation

Average response time improved through optimized server routing

Achieved stable uptime during testing and deployment phases

Key takeaway:

This wasn’t just about building features it was about shipping reliable, scalable systems.

I’ve included an architecture breakdown in the next post

DevOps #CloudEngineering #Render #Docker #CI_CD #Nginx #AgriTech #OpenToWork

FAILURE ANALYSIS & DEBUGGING

Miracle Olorunsola — Sun, 01 Mar 2026 12:00:00 +0000

What Pipeline Failures Taught Me

Failures included:

Missing tools
Incorrect build paths
Credential scope issues

Each failure improved:

Pipeline resilience
Observability
System understanding

DevSecOps is about controlled failure.
This project demonstrates hands-on experience with:

Jenkins CI/CD
Docker & Kubernetes
Terraform & AWS
Container security

Secure infrastructure design

I’m actively growing as a DevSecOps / Cloud Engineer and open to opportunities.

Secure Secrets Injection in Terraform & Jenkins

Miracle Olorunsola — Sat, 28 Feb 2026 12:00:00 +0000

Secrets are injected at runtime using:

Jenkins credentials

TF_VAR_db_username
TF_VAR_db_password

They are:

Not committed
Not logged
Not baked into images

This limits blast radius.

Provisioning AWS Infrastructure with Terraform

Miracle Olorunsola — Wed, 25 Feb 2026 12:30:00 +0000

Infrastructure is code — and should be treated that way.

Terraform manages:

VPC networking

EKS cluster

IAM permissions

Benefits:

Version control

Repeatability

Reduced misconfiguration risk

Embedding Security Gates with Trivy

Miracle Olorunsola — Mon, 23 Feb 2026 12:00:00 +0000

Security scans should:

Fail builds on HIGH/CRITICAL issues

Run automatically

Be enforced before deployment

Trivy scans every image before it’s pushed or deployed.

This shifts security left in the SDLC.
Securing Docker Image Distribution

Container registries are part of your attack surface.

Measures used:

Jenkins credentials manager

Scoped DockerHub tokens

No plaintext secrets

Supply chain security is DevSecOps responsibility.

Dockerizing Applications for CI/CD

Miracle Olorunsola — Sat, 21 Feb 2026 12:00:00 +0000

Docker is more than packaging; it’s runtime security.

In this project:

Backend and frontend have separate Dockerfiles
Build contexts are explicitly defined

Images are tagged deterministically

Key lessons:

Dockerfile location matters
Build context errors break pipelines
Reproducibility beats cleverness