From 909f2338efb5fe2660009ecd9552cc366214b843 Mon Sep 17 00:00:00 2001 From: Elvis Otieno <125451537+the1Riddle@users.noreply.github.com> Date: Mon, 4 Dec 2023 15:22:11 +0300 Subject: [PATCH] Revert "Web stack debugging #1" --- .../0-nginx_likes_port_80 | 8 ---- .../1-debugging_made_short | 4 -- 0x0E-web_stack_debugging_1/README.md | 44 ------------------- 3 files changed, 56 deletions(-) delete mode 100644 0x0E-web_stack_debugging_1/0-nginx_likes_port_80 delete mode 100644 0x0E-web_stack_debugging_1/1-debugging_made_short delete mode 100644 0x0E-web_stack_debugging_1/README.md diff --git a/0x0E-web_stack_debugging_1/0-nginx_likes_port_80 b/0x0E-web_stack_debugging_1/0-nginx_likes_port_80 deleted file mode 100644 index ae66a4e..0000000 --- a/0x0E-web_stack_debugging_1/0-nginx_likes_port_80 +++ /dev/null @@ -1,8 +0,0 @@ -#!/usr/bin/env bash -# finding out what’s keeping Ubuntu container’s Nginx installation from.. -# listening on port 80. -# Then, writing a Bash script with a minimum num of commands t automate the fix -sudo sed -i "s/ipv6only=on//" /etc/nginx/sites-available/default -sudo rm -f /etc/nginx/sites-enabled/default -sudo ln -s /etc/nginx/sites-available/default /etc/nginx/sites-enabled/default -sudo service nginx restart diff --git a/0x0E-web_stack_debugging_1/1-debugging_made_short b/0x0E-web_stack_debugging_1/1-debugging_made_short deleted file mode 100644 index b333130..0000000 --- a/0x0E-web_stack_debugging_1/1-debugging_made_short +++ /dev/null @@ -1,4 +0,0 @@ -#!/usr/bin/env bash -# my short version of task 0, making it short N sweet -sed -i 's/8080/80/g' /etc/nginx/sites-enabled/default -pkill -1 nginx \ No newline at end of file diff --git a/0x0E-web_stack_debugging_1/README.md b/0x0E-web_stack_debugging_1/README.md deleted file mode 100644 index 10fc058..0000000 --- a/0x0E-web_stack_debugging_1/README.md +++ /dev/null @@ -1,44 +0,0 @@ -#

Web stack debugging #1

- -- this involves identifying and fixing issues at various levels of the web development stack, including the front end, back end, and the server. - -##

![image](https://github.com/the1Riddle/alx-system_engineering-devops/assets/125451537/7287d3c2-b790-4654-9f97-4e57e320baf8)

- -## How to approach web stack debugging: - -###

Back-End Debugging:

- - 1. Server Logs: - > Check server logs for errors and warnings. - > Analyze logs to identify patterns or specific issues. - - 2. Database Debugging: - > Ensure database connections are established correctly. - > Check database logs for errors. - > Verify that database queries are returning the expected results. - - 3. API Testing: - > Test API endpoints using tools like Postman or cURL. - > Inspect API responses for errors and unexpected behavior. - - 4. Code Profiling: - > Use profiling tools to identify performance bottlenecks in your server-side code. - > Profile database queries and optimize slow-performing queries. - -###

Infrastructure Debugging:

- - 1. Server Configuration: - > Verify server configurations for web servers (e.g., Apache, Nginx). - > Check for any misconfigurations that may lead to issues. - - 2. Load Balancing: - > If applicable, check load balancing configurations. - > Ensure that requests are distributed evenly among server instances. - - 3. Firewall and Security: - > Check firewall settings for any restrictions. - > Verify that security configurations are not blocking legitimate requests. - - 4. Resource Monitoring: - > Monitor server resources (CPU, memory, disk space) to identify resource-related issues. - > Use tools like top or server monitoring services.