<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by David Favour on Medium]]></title>
        <description><![CDATA[Stories by David Favour on Medium]]></description>
        <link>https://medium.com/@dxelpraise?source=rss-efffec755e72------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*iN0TZUvcuna7lSSH.</url>
            <title>Stories by David Favour on Medium</title>
            <link>https://medium.com/@dxelpraise?source=rss-efffec755e72------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 15:08:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dxelpraise/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Building a Beginner-Friendly Fintech Payment Switch with FastAPI]]></title>
            <link>https://medium.com/@dxelpraise/building-a-beginner-friendly-fintech-payment-switch-with-fastapi-6f43cc5b1bac?source=rss-efffec755e72------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f43cc5b1bac</guid>
            <dc:creator><![CDATA[David Favour]]></dc:creator>
            <pubDate>Mon, 09 Feb 2026 11:50:33 GMT</pubDate>
            <atom:updated>2026-02-09T11:50:33.396Z</atom:updated>
            <content:encoded><![CDATA[<p>This project demonstrates how a real-world fintech payment switch works using a simplified, beginner-friendly architecture. The goal is to simulate how financial transactions move through a system while exposing the full DevOps lifecycle behind it.</p><p>A payment switch is the core engine that routes transactions between banks, validates requests, ensures reliability, and records activity. In this implementation, we model that behavior using a microservices approach powered by FastAPI.</p><p>The system is composed of:</p><ul><li><strong>API Gateway (FastAPI)</strong> — Receives payment requests and validates input.</li><li><strong>Switch Core Service</strong> — Simulates transaction routing and processing logic.</li><li><strong>Bank Service</strong> — Represents an external banking system.</li><li><strong>PostgreSQL</strong> — Stores transaction records.</li><li><strong>Redis</strong> — Provides caching for performance optimization.</li><li><strong>RabbitMQ</strong> — Handles asynchronous message queuing for background processing.</li><li><strong>Docker Compose</strong> — Orchestrates all services locally in a reproducible environment.</li><li><strong>Structured Logging</strong> — Tracks transaction flow for observability and debugging.</li></ul><p>When a user submits a payment request:</p><ol><li>The API validates and accepts the request.</li><li>The transaction is published to RabbitMQ.</li><li>A worker service consumes the message in the background.</li><li>The switch core processes the transaction.</li><li>The result is stored in PostgreSQL.</li><li>Logs capture every stage for monitoring and troubleshooting.</li></ol><p>This architecture mirrors real fintech systems but remains simple enough for beginners to understand. It introduces core DevOps concepts such as containerization, service communication, message queues, caching, logging, networking, and background workers all in a controlled local environment.</p><p>In real life, companies like:</p><ul><li>Interswitch</li><li>Visa</li><li>Flutterwave</li><li>Paystack, etc</li></ul><p>Do not store your money, they <strong>route transactions between banks</strong>.</p><p>This FastAPI project simulates that routing layer.</p><h3>Architecture Overview</h3><p>Our simulation includes:</p><ul><li><strong>FastAPI API Service</strong></li><li><strong>PostgreSQL (Database)</strong></li><li><strong>Redis (Cache)</strong></li><li><strong>RabbitMQ (Message Queue)</strong></li><li><strong>Worker Service</strong></li><li><strong>Docker Containers</strong></li></ul><h3>Flow:</h3><p><em>Client → FastAPI → Queue → Worker → Database</em></p><p>Each component runs in its own container.</p><h3>What Happens When You Send a Payment?</h3><p>When we send a POST request:</p><p><em>curl -X POST \<br> ‘</em><a href="http://localhost:8000/payments&#39;"><em>http://localhost:8000/payments&#39;</em></a><em> \<br> -H ‘Content-Type: application/json’ \<br> -d ‘{<br> “sender”: “alice”,<br> “receiver”: “bob”,<br> “amount”: 100<br>}’</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*10AIUpV9rYu9pdCAVYzPjg.png" /></figure><p>We receive:</p><p><em>{<br> “transaction_id”: 3,<br> “status”: “PROCESSING”<br>}</em></p><p>And HTTP status:</p><p><em>200 OK</em></p><p>Exactly like in the screenshot above.</p><p>But why <strong>PROCESSING</strong> and not <strong>SUCCESS</strong>?</p><p>Because this system is <strong>asynchronous by design</strong>. An <strong>asynchronous architecture</strong> means that system components interact without waiting for a direct, immediate response. Instead of a “blocking” request-response cycle, the sender dispatches a message such as a payment instruction to a middle layer (like a message queue) and immediately continues other work.</p><h3>Real Fintech Architecture Is Asynchronous</h3><p>In production payment systems:</p><ol><li>Client sends payment request</li><li>Switch validates input</li><li>Switch pushes transaction into a message queue</li><li>Worker service processes transaction</li><li>Bank updates balances</li><li>Status changes later</li></ol><p>The client is not blocked while processing happens.</p><p>That’s why we return:</p><p><em>{<br> “status”: “PROCESSING”<br>}</em></p><p>This prevents:</p><ul><li>Long response times</li><li>API timeouts</li><li>System bottlenecks</li><li>Cascading failures</li></ul><h3>What the Screenshot Proves</h3><p>The Swagger UI shows:</p><ul><li>Endpoint: POST /payments</li><li>Response Code: 200</li><li>JSON response with transaction_id</li><li>Status: PROCESSING</li></ul><p>This means:</p><p>✔ FastAPI validated request<br> ✔ Transaction inserted into database<br> ✔ Message published to queue<br> ✔ Worker will process it asynchronously</p><p>Uvicorn handled the HTTP layer. Docker handled container runtime.<br> Linux handled process scheduling. Postgres handled persistence.</p><h3>What This Teaches About DevOps</h3><p>This app demonstrates:</p><h3>Application Layer</h3><ul><li>REST API</li><li>JSON validation</li><li>Request lifecycle</li></ul><h3>Process Layer (Linux)</h3><ul><li>Uvicorn runs as a process</li><li>Docker isolates namespaces</li><li>Kernel schedules CPU time</li></ul><h3>Networking</h3><ul><li>Docker bridge network</li><li>Service-to-service communication</li><li>TCP handshake between containers</li></ul><h3>Storage</h3><ul><li>PostgreSQL persistent volume</li><li>Redis in-memory caching</li></ul><h3>Messaging</h3><ul><li>RabbitMQ queue decouples services</li><li>Prevents synchronous blocking</li></ul><h3>Observability</h3><ul><li>Logs emitted to stdout</li><li>Docker captures logs</li><li>Ready for Prometheus/Grafana</li></ul><h3>How To Test It</h3><h4>Step 1 — Start Services</h4><p><em>docker compose up — build</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wnosvRSrFA3Pamp6H3IYpQ.png" /></figure><p><strong>Step 2 — Open Swagger</strong></p><p><a href="http://localhost:8000/docs">http://localhost:8000/docs</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*houUF53j8ecfL-L3SylbuA.png" /></figure><p><strong>Step 3 — Send Payment</strong></p><p><em>{<br> “sender”: “alice”,<br> “receiver”: “bob”,<br> “amount”: 100<br>}</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*10AIUpV9rYu9pdCAVYzPjg.png" /></figure><h3>What Actually Happens When You Send Payment</h3><p>When you POST to:</p><p><em>POST /payments</em></p><p>The system flow is:</p><ol><li><strong>API container</strong></li></ol><ul><li>Receives request</li><li>Saves transaction to DB (or prepares it)</li><li>Publishes message to RabbitMQ queue</li><li>Returns response immediately</li></ul><ol><li><strong>Worker container (background service)</strong></li></ol><ul><li>Listens to RabbitMQ queue</li><li>Picks up the transaction message</li><li>Processes it</li></ul><p><strong>Step 4 Check Logs</strong></p><p><em>docker-compose logs fintech-payment-switch-simulation-worker-1</em></p><p>You’ll see transaction processing in background.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sVvkTk3uwLE5df0RrrekWQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f43cc5b1bac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Beginner-Friendly Linux DevOps Monitoring, Backup & Alerting Project (with Email Alerts)]]></title>
            <link>https://medium.com/@dxelpraise/building-a-beginner-friendly-linux-devops-monitoring-backup-alerting-project-with-email-alerts-ab2ed1fbf910?source=rss-efffec755e72------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab2ed1fbf910</guid>
            <dc:creator><![CDATA[David Favour]]></dc:creator>
            <pubDate>Fri, 30 Jan 2026 14:55:22 GMT</pubDate>
            <atom:updated>2026-01-30T14:55:22.161Z</atom:updated>
            <content:encoded><![CDATA[<p>This guide walks you through a <strong>hands-on Linux DevOps project</strong> designed for beginners transitioning into DevOps or system administration.</p><p>You will build a <strong>monitoring, backup, and alerting system</strong> using Bash scripts, cron automation, and <strong>real email alerts via Postfix</strong>, all running on a Linux server.<br> This project is simple enough to learn from, yet practical enough to showcase in a DevOps portfolio.</p><h3>Project Overview</h3><p>By the end of this project, you will have</p><ul><li>User activity and sudo monitoring</li><li>System resource monitoring (CPU, memory, disk)</li><li>Automated backups</li><li>Email alerting using Postfix</li><li>Centralized alert dispatching</li><li>Cron-based automation</li></ul><p><strong>Project Structure:</strong></p><p>linux-project/<br>├── scripts/<br>│ ├── user_setup.sh<br>│ ├── monitoring.sh<br>│ ├── log_audit.sh<br>│ ├── backup.sh<br>│ └── alert_dispatcher.sh<br>├── security_alert.sh<br>├── email_alert.sh<br>├── backup_verify.sh<br>└── README.md</p><h3>Step 1 — Set Up the Project Directory</h3><p>Create a clean workspace for all scripts:</p><p><em>mkdir -p ~/linux-project/scripts<br>cd ~/linux-project<br>touch scripts/{user_setup.sh,monitoring.sh,log_audit.sh,backup.sh,alert_dispatcher.sh}<br>touch security_alert.sh email_alert.sh backup_verify.sh README.md</em></p><h3>Step 2 — Understanding Multi-User Linux &amp; Sudo Activity</h3><p>Linux servers are multi-user systems.<br> Administrative actions are logged and can be monitored.</p><p>Authentication logs are stored in:</p><p><em>/var/log/auth.log</em></p><p>To view recent sudo activity:</p><p><em>grep “sudo” /var/log/auth.log | tail -n 5</em></p><p>This is the foundation for security alerting.</p><h3>Step 3 — Security Alert Script (Sudo Monitoring)</h3><p>Create a script that detects recent sudo commands.</p><p><em>nano ~/linux-project/security_alert.sh</em></p><p><strong>Paste:</strong></p><p><em>#!/bin/bash</em></p><p><em>LOG_FILE=”/var/log/auth.log”<br>LAST_SUDO=$(grep “sudo:” “$LOG_FILE” | grep “COMMAND=” | tail -n 1)</em></p><p><em>if [[ -n “$LAST_SUDO” ]]; then<br> echo “SUDO ALERT DETECTED:”<br> echo “$LAST_SUDO”<br>else<br> echo “No new sudo activity detected.”<br>fi</em></p><p><strong>Make it executable:</strong></p><p><em>chmod +x ~/linux-project/security_alert.sh</em></p><p><strong>Test it:</strong></p><p><em>sudo ls /root<br>~/linux-project/security_alert.sh</em></p><p><strong>Step 4 — Install &amp; Configure Postfix (Email Alerting)</strong></p><p>To enable real email alerts, install Postfix and mail utilities:</p><p><em>sudo apt update<br>sudo apt install postfix mailutils -y</em></p><p><strong>During installation:</strong></p><ul><li>Select Local only</li><li>Use your server hostname as the mail name</li></ul><p><strong>Verify Postfix is running:</strong></p><p><em>systemctl status postfix</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/891/1*WWqOSh59qSA62wlhOm8uGQ.png" /></figure><h4>Step 5 — Email Alert Script</h4><p>Create an email alert script that sends security notifications.</p><p><em>nano ~/linux-project/email_alert.sh</em></p><p><strong>Paste:</strong></p><p><em>#!/bin/bash</em></p><p><em>LOCAL_USER=”&lt;</em>LOCAL_USER&gt;<em>”<br>HOSTNAME=$(hostname)<br>DATE=$(date)</em></p><p><em>MESSAGE=”Security alert on $HOSTNAME at $DATE</em></p><p><em>Recent sudo activity detected on this system.”</em></p><p><em>echo “$MESSAGE” | mail -s “Linux Security Alert” “$LOCAL_USER”</em></p><p><strong>Make it executable:</strong></p><p><em>chmod +x ~/linux-project/email_alert.sh</em></p><p><strong>Test it:</strong></p><p><em>sudo ls /root<br>/usr/local/bin/security_alert.sh<br>mail</em></p><p><strong>Step 6 — Alert Dispatcher (Central Alert Handler)</strong></p><p>Combine terminal alerts and email alerts into one dispatcher.<em><br></em>nano ~/linux-project/scripts/alert_dispatcher.sh</p><p><strong>Paste:</strong><br><em>#!/bin/bash</em></p><p><em>~/linux-project/security_alert.sh<br>~/linux-project/email_alert.sh</em></p><p><strong>Make it executable:</strong></p><p><em>chmod +x ~/linux-project/scripts/alert_dispatcher.sh</em></p><p><strong>Test:</strong></p><p><em>sudo ls /root<br>bash ~/linux-project/scripts/security_alert.sh<br>mail</em></p><h4>Step 7 — System Monitoring Script</h4><p>Create a basic monitoring script for system resources.</p><p><em>nano ~/linux-project/scripts/monitoring.sh</em></p><p><strong>Paste:</strong><br><em>#!/bin/bash</em></p><p><em>DATE=$(date)<br>CPU=$(top -bn1 | grep load | awk ‘{printf “%.2f”, $(NF-2)}’)<br>MEM=$(free -m | awk ‘NR==2{printf “%s/%sMB”, $3,$2}’)<br>DISK=$(df -h / | awk ‘NR==2{print $5}’)</em></p><p><em>echo “$DATE | CPU Load: $CPU | Memory: $MEM | Disk Usage: $DISK”</em></p><p><strong>Make executable:</strong><br><em>chmod +x ~/linux-project/scripts/monitoring.sh</em></p><p><strong>Test it:</strong><br><em>~/linux-project/scripts/monitoring.sh</em></p><p><strong>Step 8-Backup Script</strong></p><p>Create a simple backup script for critical directories.</p><p><em>nano ~/linux-project/scripts/backup.sh</em></p><p><strong>Paste:</strong><br><em>#!/bin/bash</em></p><p><em>BACKUP_DIR=~/linux-project/backups<br>mkdir -p “$BACKUP_DIR”</em></p><p><em>tar -czf “$BACKUP_DIR/system-$(date +%F).tar.gz” /etc /home/&lt;user&gt;</em></p><p><em>echo “Backup completed at $BACKUP_DIR”</em></p><p><strong>Make executable:</strong></p><p><em>chmod +x ~/linux-project/scripts/backup.sh</em></p><p><strong>Test:</strong><br><em>~/linux-project/scripts/backup.sh<br>ls -lh ~/linux-project/backups</em></p><p><strong>Step 9 Cron Automation</strong></p><p>Automate monitoring, alerting, and backups.</p><p><strong>Edit crontab:</strong><br><em>crontab -e<br></em><strong>Add:</strong><br><em>*/5 * * * * ~/linux-project/scripts/alert_dispatcher.sh<br>*/10 * * * * ~/linux-project/scripts/monitoring.sh<br>0 2 * * * ~/linux-project/scripts/backup.sh</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab2ed1fbf910" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deploying a React App with Nginx in Docker — From Scratch for Beginners]]></title>
            <link>https://medium.com/@dxelpraise/deploying-a-react-app-with-nginx-in-docker-from-scratch-for-beginners-83a9a6877492?source=rss-efffec755e72------2</link>
            <guid isPermaLink="false">https://medium.com/p/83a9a6877492</guid>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[David Favour]]></dc:creator>
            <pubDate>Wed, 28 Jan 2026 09:37:25 GMT</pubDate>
            <atom:updated>2026-01-28T09:37:25.450Z</atom:updated>
            <content:encoded><![CDATA[<h3>Deploying a React App with Nginx in Docker — From Scratch for Beginners</h3><h3>Introduction</h3><p>In this article, I’ll show you how to deploy a <strong>React application using Nginx inside Docker</strong>, starting completely from scratch.<br> This guide is designed for <strong>beginners and non-developers</strong> who want to understand how front-end apps are served in a DevOps environment.</p><p>By the end of this tutorial, you’ll have:</p><ul><li>A working React app served via Nginx in Docker</li><li>Optional Docker-in-Docker setup for DevOps experimentation</li></ul><h3>Step 1: Setting Up Ubuntu in Docker</h3><p>Even if you are not a developer, Docker allows you to run <strong>Ubuntu in an isolated environment</strong>.</p><p><em>docker pull ubuntu:24.04<br>docker run -it — name ubuntu-test ubuntu:24.04 bash</em></p><p><strong>Explanation:</strong></p><ul><li>docker pull downloads Ubuntu</li><li>docker run -it launches it interactively with bash</li><li>You are now inside Ubuntu:</li></ul><p><em>root@&lt;container_id&gt;:/#</em></p><p><strong>Install basic utilities:</strong></p><p><em>apt update &amp;&amp; apt install -y curl git wget</em></p><p><strong>Exit Ubuntu:</strong></p><p><em>exit</em></p><h3>Step 2: Prepare the Project Structure</h3><p>On your host machine, create the folders:</p><p><em>mkdir -p react-nginx-docker/app<br>mkdir react-nginx-docker/nginx<br>cd react-nginx-docker</em></p><p><strong>Folder layout:</strong></p><p>react-nginx-docker/<br>├── app/ # React app build<br>├── nginx/ # Nginx config<br>├── Dockerfile<br>├── docker-compose.yml<br>└── README.md</p><h3>Step 3: Add a Minimal React Build</h3><p>Since we’re not developers, we’ll use a <strong>pre-built React page</strong>:</p><p>app/build/index.html:</p><p><em>&lt;!DOCTYPE html&gt;<br>&lt;html&gt;<br> &lt;head&gt;<br> &lt;title&gt;React Nginx Docker Portfolio&lt;/title&gt;<br> &lt;/head&gt;<br> &lt;body&gt;<br> &lt;h1&gt;Hello React + Nginx + Docker!&lt;/h1&gt;<br> &lt;p&gt;This is a minimal React build for demonstration purposes.&lt;/p&gt;<br> &lt;/body&gt;<br>&lt;/html&gt;</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iDZjBs42OQ-iYXKrqmQGEg.png" /></figure><h3>Step 4: Configure Nginx</h3><p>Create nginx/default.conf:</p><p><em>server {<br> listen 80;<br> server_name localhost;</em></p><p><em>root /usr/share/nginx/html;<br> index index.html;</em></p><p><em>location / {<br> try_files $uri /index.html;<br> }</em><br>}</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XTKrnNxMI1pl5Y_ONk-V6Q.png" /></figure><p><strong>Explanation:</strong></p><ul><li>This serves the React app and ensures routing works.</li></ul><h3><strong>Step 5: Dockerfile</strong></h3><p><em>FROM nginx:stable-alpine</em></p><p><em>COPY app/build /usr/share/nginx/html<br>COPY nginx/default.conf /etc/nginx/conf.d/default.conf</em></p><p><em>EXPOSE 80<br>CMD [“nginx”, “-g”, “daemon off;”]</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BPnxNzTy04WsF3gxwzvkOA.png" /></figure><p><strong>Explanation:</strong></p><ul><li>Multi-stage build isn’t needed here because the app is pre-built</li><li>Nginx serves the static files</li><li>Port 80 is exposed</li></ul><h3>Step 6: Optional Docker Compose for Docker-in-Docker</h3><p>For advanced DevOps experiments:</p><p>docker-compose.yml:</p><p><em>version: “3.9”</em></p><p><em>services:<br> react-app:<br> build: .<br> ports:<br> — “8080:80”<br> depends_on:<br> — dind<br> environment:<br> — DOCKER_HOST=tcp://dind:2375</em></p><p><em>dind:<br> image: docker:24-dind<br> privileged: true<br> ports:<br> — “2375:2375”<br> environment:<br> — DOCKER_TLS_CERTDIR=</em></p><p><strong>Explanation:</strong></p><ul><li>dind runs Docker inside Docker</li><li>Useful for DevOps workflows and CI/CD simulation</li></ul><h3>Step 7: Build and Run</h3><p>Build Docker image:</p><p><em>docker build -t react-nginx-app .</em></p><p>Run container:</p><p><em>docker run -d -p 8080:80 — name my-react-app react-nginx-app</em></p><p>Check running containers:</p><p><em>docker ps</em></p><p>Open your browser → <a href="http://localhost:8080/">http://localhost:8080</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*-bxif9GFSpOVtCAlirvSQg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83a9a6877492" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting Up NGINX on an Ubuntu Server on AWS]]></title>
            <link>https://medium.com/@dxelpraise/setting-up-nginx-on-an-ubuntu-server-on-aws-720928f4ec25?source=rss-efffec755e72------2</link>
            <guid isPermaLink="false">https://medium.com/p/720928f4ec25</guid>
            <category><![CDATA[aws-ec2]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[nginx-set]]></category>
            <dc:creator><![CDATA[David Favour]]></dc:creator>
            <pubDate>Thu, 30 Jan 2025 11:03:48 GMT</pubDate>
            <atom:updated>2025-01-30T12:35:24.317Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Setting Up NGINX on an Ubuntu Server on AWS</strong></p><p>In this blog post, I will walk through setting up and configuring an NGINX web server on a fresh Ubuntu instance hosted on AWS. This task was a valuable learning experience, allowing me to gain hands-on exposure to web server configurations and cloud deployment.</p><h3>Task Objective</h3><p>The objective was to install and configure NGINX to serve a custom HTML page with the message:</p><blockquote><em>Welcome to DevOps Stage 0 — [My name]/ [Slack Username]</em></blockquote><h3>Approach</h3><h4>Step 1: Launch an Ubuntu EC2 Instance on AWS</h4><ol><li>Log into the AWS Management Console and navigated to the EC2 dashboard.</li><li>select the option to launch a new instance, choosing Ubuntu Server 20.04 LTS as the operating system.</li><li>After configuring instance details and security group settings (allowing HTTP and SSH traffic), launch the instance.</li></ol><h4>Step 2: Connecting to the Instance via SSH</h4><ol><li>Download the private key (.pem) file during instance creation.</li><li>On the terminal, navigate to the directory containing the key file and ran the following command to set the correct permissions:</li></ol><ul><li>chmod 400 &quot;keyname&quot;.pem</li></ul><p>3. Connect to the instance with the command:</p><ul><li>ssh -i &quot;keyname&quot; ubuntu@&lt;EC2-public-IP&gt;</li></ul><h4>Step 3: Installing NGINX</h4><p>Once connected to the instance, I ran the following commands to update the package list and install NGINX:</p><pre>sudo apt update<br>sudo apt install nginx -y</pre><p>I verified that NGINX was running using:</p><pre>sudo systemctl status nginx</pre><h4>Step 4: Configuring the Custom HTML Page</h4><ol><li>navigate to the default web directory:</li></ol><ul><li>cd /var/www/html</li></ul><p>2. I created a custom index.html file with the required message:</p><ul><li>sudo nano index.html</li></ul><p>3. The content of the file was:</p><ul><li>&lt;html&gt; <br>&lt;head&gt;<br>&lt;title&gt;DevOps Stage 0&lt;/title&gt;<br>&lt;/head&gt; <br>&lt;body&gt; <br>&lt;h1&gt;Welcome to DevOps Stage 0 - David Favour/@David Favour&lt;/h1&gt; &lt;/body&gt; <br>&lt;/html&gt;</li></ul><p>4. Save and exited the file.</p><h4>Step 5: Verifying the Configuration</h4><p>Access the web server from the browser by entering the public IP address of the EC2 instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y7nivhtsEvea5ulBoTjV-g.png" /></figure><p>The custom HTML message was successfully displayed.</p><h3>Challenges and Solutions</h3><p><strong>1. Permission Issues:</strong> I initially encountered permission errors when editing files in the /var/www/html directory. Using sudo resolved this issue.</p><p><strong>2. Security Group Configuration:</strong> Initially, I couldn’t access the web server due to blocked HTTP traffic. I resolved this by updating the security group to allow inbound traffic on port 80.</p><h3>Key Learnings</h3><p>This task provided valuable insights into:</p><ul><li>Configuring a web server using NGINX.</li><li>Navigating and managing an Ubuntu server on AWS.</li><li>Resolving common permission and network configuration issues.</li></ul><h3>Professional Growth and Reflection</h3><p>This experience solidified my understanding of cloud-based server management and web server configurations. As I transition into a cloud-focused DevOps role, these foundational skills will be instrumental in my professional development.</p><h3>References</h3><ul><li>DevOps Engineers — <a href="https://hng.tech/hire/devops-engineers">https://hng.tech/hire/devops-engineers</a></li><li>Cloud Engineers — <a href="https://hng.tech/hire/cloud-engineers">https://hng.tech/hire/cloud-engineers</a></li><li>Site Reliability Engineers — <a href="https://hng.tech/hire/site-reliability-engineers">https://hng.tech/hire/site-reliability-engineers</a></li><li>Platform Engineers — <a href="https://hng.tech/hire/platform-engineers">https://hng.tech/hire/platform-engineers</a></li><li>Infrastructure Engineers — <a href="https://hng.tech/hire/infrastructure-engineers">https://hng.tech/hire/infrastructure-engineers</a></li><li>Kubernetes Specialists — <a href="https://hng.tech/hire/kubernetes-specialists">https://hng.tech/hire/kubernetes-specialists</a></li><li>AWS Solutions Architects — <a href="https://hng.tech/hire/aws-solutions-architects">https://hng.tech/hire/aws-solutions-architects</a></li><li>Azure DevOps Engineers — <a href="https://hng.tech/hire/azure-devops-engineers">https://hng.tech/hire/azure-devops-engineers</a></li><li>Google Cloud Engineers — <a href="https://hng.tech/hire/google-cloud-engineers">https://hng.tech/hire/google-cloud-engineers</a> • CI/CD Pipeline Engineers — <a href="https://hng.tech/hire/ci-cd-pipeline-engineers">https://hng.tech/hire/ci-cd-pipeline-engineers</a></li><li>Monitoring/Observability Engineers — <a href="https://hng.tech/hire/monitoring-observability-engineers">https://hng.tech/hire/monitoring-observability-engineers</a></li><li>Automation Engineers — <a href="https://hng.tech/hire/automation-engineers">https://hng.tech/hire/automation-engineers</a></li><li>Docker Specialists — <a href="https://hng.tech/hire/docker-specialists">https://hng.tech/hire/docker-specialists</a></li><li>Linux Developers — <a href="https://hng.tech/hire/linux-developers">https://hng.tech/hire/linux-developers</a></li><li>PostgreSQL Developers — <a href="https://hng.tech/hire/postgresql-developers">https://hng.tech/hire/postgresql-developers</a></li></ul><p>Completing this task has been both challenging and rewarding. I look forward to applying these skills to more complex DevOps projects in the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=720928f4ec25" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IMPACTS OF FLUTERWAVE IN OUR SOCIETY]]></title>
            <link>https://medium.com/@dxelpraise/impacts-of-fluterwave-in-our-society-92ce6a87b341?source=rss-efffec755e72------2</link>
            <guid isPermaLink="false">https://medium.com/p/92ce6a87b341</guid>
            <category><![CDATA[payments]]></category>
            <dc:creator><![CDATA[David Favour]]></dc:creator>
            <pubDate>Tue, 03 Oct 2017 17:28:52 GMT</pubDate>
            <atom:updated>2017-10-03T17:43:08.531Z</atom:updated>
            <content:encoded><![CDATA[<p>IMPACTS OF FLUTERWAVE IN OUR SOCIETY</p><p>by david umoren</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*TkSBXzADm-uvTYu8NN6jGQ.jpeg" /></figure><p>Some few years back making and receiving payments online in Nigeria was not just tedious but also for the brave folks.At some point the Central Bank of Nigeria said that every online transaction had to be “tokenized”( i.e. confirmed by a one-time password). This soon became a challenge because making recurring payments were somewhat impossible to execute. As a result, the only way to execute online subscription services was using premium SMS. This was restricted by another regulation, this time from the National Communications Commission capping transaction size at N200 (roughly $1). Telcoms and their service provider partners used to charge a service fee that ranged from 60% to 80%. All that is history now. With flutterwave playing a major role in the shift<br><br>Flutterwave bills itself as an African digital payment infrastructure company that helps companies send and receive payments across Africa with one API. This allow businesses accept and disburse payments from MasterCard, Visa, Verve, Mobile Money, and even cash tokens and e-wallets on any channel(web, Mobile, ATM &amp; POS) in different African countries and around the world. Believe me flutterwave is turning the African local market space to a digital global market community</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*uuDUm3Af_quUHPTPfU-i5A.jpeg" /></figure><p>Your payment is protected with chargeback insurance and guaranteed to land in the right account by the next day – this will atleast reduce the heart failures and high BP for clients.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/1*ESW5KKJskJNiM5Amc9BV3w.jpeg" /></figure><p>Your business/product is not just limited to local audience, with few clicks you can expand it to more countries – honestly this means GROWTH in all ramifications. If you just got into ecommerce I must say that you came at THE RIGHT TIME. The most daunting thing about ecommerce before now was the payment process.</p><p>Apart from the benefits afore mentioned which are fluterwave’s core functions, fluterwave also plays supportive role by investing in startups thus helping them expand and grow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92ce6a87b341" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 STEPS IN MAKING A GOOD DESIGN]]></title>
            <link>https://medium.com/@dxelpraise/5-steps-in-making-a-good-design-df26ce26d702?source=rss-efffec755e72------2</link>
            <guid isPermaLink="false">https://medium.com/p/df26ce26d702</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[David Favour]]></dc:creator>
            <pubDate>Sun, 10 Sep 2017 18:16:16 GMT</pubDate>
            <atom:updated>2017-09-11T00:42:44.354Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>5 STEPS IN MAKING A GOOD DESIGN</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jPbyWlJTxwSb1gNuoOP4vw.jpeg" /></figure><p>by <a href="https://medium.com/u/efffec755e72">David Favour</a></p><blockquote>“Design is a solution to a problem&quot;-john maeda. Good design is not just what looks good. It also needs to perform, convert, astonish, and fulfill its purpose. <br>Below are some of the basic steps/tips in making a good design.</blockquote><p><strong>MAKE A SKETCH</strong>: Before you start designing on your computer, you need to make some sketches on paper specifying what items you want to include and where they should be positioned on your design. This will guide you throughout your design. For me this is the first stage in a design process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*DLJBPmUBL1ZrKADuoiz6uA.jpeg" /></figure><p><strong>CHOICE OF FONTS</strong>: The quality of your content is the most important thing, but how you present that content is by choosing the right font and layout is a close second. according to Meghan lazier, a typeface could be seen as a shoe. A man can wear faded jeans, torn shirts and unkempt hair.but if his shoes are clean and polished people will notice and he is perceived positively wearing those shoes. An expensive suit with dirty shoes creates a bad impression. Similarly, your font and typefaces can be seen as the &quot;shoes&quot; of your design. A French poet Claudel put it thus &quot;the secret of typeface is that it speaks&quot; that is your font type determines how well your designs are percieved When choosing your font type you should have the following in mind.<br> -Readability <br> -Legibility <br> -Design intent<br> -Aesthetics</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*svPj0uunyGbVe5_ruWNp2w.png" /></figure><p><strong>CHOICE OF COLOUR</strong>: According to sigmund freud, &quot;colour is the mother tongue of the subconciousness&quot;. colour is one of the most powerful element in design, it has tremendous expeessive qualities and understanding the use of colour is crucial to effective composition in design. Choosing a more appealing colour helps designer communicate effectively with users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rG1hHjbqg4C_3-bL7Wg1LA.jpeg" /></figure><p><strong>WHITE SPACES</strong>: White space are intentional and deliberate space (not the accidental left over space).See it as the portion of the designed items that are left unmarked. In designing try not to get your work clutter things up because it will make your work unreadable. White space helps in readability, it makes your audience comfortable and also makes your design more appealing. Using white space judiciously and conciously is one important part of a good design</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/496/1*iEzrwtMYw4qLJu0Nh68LdQ.jpeg" /></figure><p><strong>PROPER ALIGNMENT</strong>: The word alignment takes it origin from &quot;line&quot; . It is placement of text, images etc so that they line up properly. Aligning elements allow them to create a more ordered design it creates harmony too. Always ensure that your elements are properly aligned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*ttF0pKunnbQNHk-5wvXPgw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df26ce26d702" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>