HNG Internship Week 1

Omoruyi Emmanuel Osakue — Fri, 07 Feb 2025 22:30:23 +0000

So... As I said, beginnings are always easy, and HNG dropped a big one on me this week making me think. How about I try to push beyond my capabilities?
So far I have little prerequisite with Python and API technologies, lame I know. But if you're reading this it means I overcame so I implore you to read through this and I'll tell you how

Steps to Deploy on EC2:

Launch an EC2 Instance:

Choose a Linux AMI.
Select an appropriate instance type (t2.micro).
Configure security groups to allow inbound HTTP traffic (port 80) and SSH (port 22).
Connect to your EC2 Instance: Use SSH to connect to your instance.

Install Python and Dependencies:

sudo apt update -y  # Update system packages
sudo apt install python3.12-venv  # Create a virtual environment

You can clone your GitHub repository and change into it, then activate virtual environment.

python3 -m venv venv 
pip install -r requirements.txt # Install dependencies

Create a WSGI file (wsgi.py):

touch wsgi.py

from app import app  # Replace app with your Flask app's name

if __name__ == "__main__":
    app.run()

Run with Gunicorn (Recommended for Production):

gunicorn --bind :8000 wsgi:app  # Run Gunicorn on port 8000

You could run this in the background using nohup or screen so it continues to run after you disconnect from SSH.

Configure a Reverse Proxy (Nginx or Apache): sudo apt install nignx -y

A reverse proxy is highly recommended for production. It handles static files, load balancing, and more. Here's a basic Nginx configuration example:

server {
    listen 80;
    server_name your_ec2_public_ip_or_dns;  # Replace with your EC2 instance's public IP or DNS

    location / {
        proxy_pass http://127.0.0.1:8000;  # Forward requests to Gunicorn
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
    }
}

Place this configuration in /etc/nginx/conf.d/your_app.conf and restart Nginx:

sudo systemctl restart nginx.

Get your EC2 Public IP or DNS: You can find this in the EC2 console. Use this to access your API: http://54.204.77.176/api/classify-number?number=371

HNG Internship Begins

Omoruyi Emmanuel Osakue — Thu, 30 Jan 2025 10:03:17 +0000

Beginnings are always easy, for example, this is the beginning of my 8-week internship journey with HNG, and as excited as I am, I am resolved to overcome any challenges I would likely encounter in this program's tasks. That said, let us begin.

DevOps Stage O Task

Interns are tasked with setting up and configuring NGINX on a fresh Ubuntu server.

Solution

For this task, I will use AWS Cloud because I am familiar with it, but as I've stated, I am challenging myself, so expect this task to be redone in other cloud providers' compute instances.
First I will begin by launching the AWS compute--instance EC2, picking Ubuntu AMI, and allowing ports 22 and 80. Next, I connect to the instance via SSH

After getting into the server I would run an update and install NGINX with the following command

sudo apt update & sudo apt install nginx -y

Now I'll navigate to the directory where my webpage will be served

cd /var/www/html/

Once there I create a new file using sudo permission and add my HTML code

sudo vi index.html

<!DOCTYPEhtml>
<html>
        <body>
                <h1>Welcome to DevOps Stage 0</h1>
                <p>Omoruyi Emmanuel Osakue/Omoruyi</p>
        </body>
</html>

Next, we run a restart for the service

sudo service nginx restart

Let’s check if everything works as it should. Open our newly created site in a web browser.

Everything works as it should. We have just configured the Nginx web server.

Now while working on this project I initially tried editing my HTML file in the /www/html/ directory without sudo permissions which of course failed after which I learned to use the sudo permissions

This task demonstrates my ability to work with basic web server configurations and deliver a functional web server.

DEV Community: Omoruyi Emmanuel Osakue