DEV Community: tundek

Resolving SPF and MX records for rodamour.com

tundek — Thu, 16 Jan 2025 10:27:01 +0000

To resolve the SPF and MX record issues for your domain, follow these steps:

Add an SPF Record The Sender Policy Framework (SPF) is used to specify which mail servers are authorized to send emails on behalf of your domain.

SPF Record Value Example:

v=spf1 include:spf.protection.outlook.com -all

Adjust the include: part depending on your email provider. For example:

Google Workspace: v=spf1 include:_spf.google.com -all
Microsoft 365: v=spf1 include:spf.protection.outlook.com -all
Custom Mail Server: Use your mail server's IP or domain.
Steps to Add SPF Record:

Log in to your DNS hosting provider.
Add a new DNS record:
Type: TXT
Host/Name: @ (or your domain name, e.g., rodarmour.com)
Value: The SPF record value provided above.
Save the record and wait for DNS propagation (can take a few hours).

Add an MX Record MX (Mail Exchange) records specify the mail servers responsible for receiving emails for your domain.

MX Record Value Example: If you're using Google Workspace:

Priority: 1
Value: aspmx.l.google.com
Additional Google Workspace records:

Priority: 5 Value: alt1.aspmx.l.google.com Priority: 5 Value: alt2.aspmx.l.google.com Priority: 10 Value: alt3.aspmx.l.google.com Priority: 10 Value: alt4.aspmx.l.google.com

If you're using Microsoft 365:

Priority: 0
Value: .mail.protection.outlook.com
For custom servers, consult your email service provider for the correct MX records.

Steps to Add MX Record:

Log in to your DNS hosting provider.
Add a new DNS record:
Type: MX
Host/Name: @ (or your domain name, e.g., rodarmour.com)
Value: MX server address (e.g., aspmx.l.google.com for Google or yourdomain.mail.protection.outlook.com for Microsoft 365).
Priority: Set as per the provider's recommendation (e.g., 1 or 0 for primary mail servers).
Save the record and wait for DNS propagation.

Deploying any LAMP Stack Application with Advanced Bash Script

tundek — Fri, 03 Jan 2025 09:48:31 +0000

Hi Guyss!! Yeah i know i know i know, it's being a while i posted and you must be wondering where this guy was and surely missed my piece.

Well i have been learning more to provide you with some advanced topics and i hope it helps.

Today we will be delving into a topic we are familiar with but in a grand style, talking about automating any LAMP stack application however, we will be writing the script for each and every step without any manual input from your side.

Let's get into it:

There is a total of 4 major steps involved in installing and automating the LAMP stack App

1. Deploying Pre-Requisites, Installing Firewalld

2. Deploying & Configure the Database, Installing MariaDB (You can use MySql, choice is yours)

3. Deploying & Configure the web server, Installing httpd,php, php-mysqlnd

4. Testing

Let's explore the major steps and see how it works

#!/bin/bash
#
# Automate ECommerce Application Deployment
# Author: Mumshad Mannambeth

#######################################
# Print a message in a given color.
# Arguments:
#   Color. eg: green, red
#######################################
function print_color(){
  NC='\033[0m' # No Color

  case $1 in
    "green") COLOR='\033[0;32m' ;;
    "red") COLOR='\033[0;31m' ;;
    "*") COLOR='\033[0m' ;;
  esac

  echo -e "${COLOR} $2 ${NC}"
}

#######################################
# Check the status of a given service. If not active exit script
# Arguments:
#   Service Name. eg: firewalld, mariadb
#######################################
function check_service_status(){
  service_is_active=$(sudo systemctl is-active $1)

  if [ $service_is_active = "active" ]
  then
    echo "$1 is active and running"
  else
    echo "$1 is not active/running"
    exit 1
  fi
}

#######################################
# Check the status of a firewalld rule. If not configured exit.
# Arguments:
#   Port Number. eg: 3306, 80
#######################################
function is_firewalld_rule_configured(){

  firewalld_ports=$(sudo firewall-cmd --list-all --zone=public | grep ports)

  if [[ $firewalld_ports == *$1* ]]
  then
    echo "FirewallD has port $1 configured"
  else
    echo "FirewallD port $1 is not configured"
    exit 1
  fi
}

#######################################
# Check if a given item is present in an output
# Arguments:
#   1 - Output
#   2 - Item
#######################################
function check_item(){
  if [[ $1 = *$2* ]]
  then
    print_color "green" "Item $2 is present on the web page"
  else
    print_color "red" "Item $2 is not present on the web page"
  fi
}



echo "---------------- Setup Database Server ------------------"

# Install and configure firewalld
print_color "green" "Installing FirewallD.. "
sudo yum install -y firewalld

print_color "green" "Installing FirewallD.. "
sudo systemctl start firewalld
sudo systemctl enable firewalld

# Check FirewallD Service is running
check_service_status firewalld

# Install and configure Maria-DB
print_color "green" "Installing MariaDB Server.."
sudo yum install -y mariadb-server

print_color "green" "Starting MariaDB Server.."
sudo systemctl start mariadb
sudo systemctl enable mariadb

# Check FirewallD Service is running
check_service_status mariadb

# Configure Firewall rules for Database
print_color "green" "Configuring FirewallD rules for database.."
sudo firewall-cmd --permanent --zone=public --add-port=3306/tcp
sudo firewall-cmd --reload

is_firewalld_rule_configured 3306


# Configuring Database
print_color "green" "Setting up database.."
cat > setup-db.sql <<-EOF
  CREATE DATABASE ecomdb;
  CREATE USER 'ecomuser'@'localhost' IDENTIFIED BY 'ecompassword';
  GRANT ALL PRIVILEGES ON *.* TO 'ecomuser'@'localhost';
  FLUSH PRIVILEGES;
EOF

sudo mysql < setup-db.sql

# Loading inventory into Database
print_color "green" "Loading inventory data into database"
cat > db-load-script.sql <<-EOF
USE ecomdb;
CREATE TABLE products (id mediumint(8) unsigned NOT NULL auto_increment,Name varchar(255) default NULL,Price varchar(255) default NULL, ImageUrl varchar(255) default NULL,PRIMARY KEY (id)) AUTO_INCREMENT=1;

INSERT INTO products (Name,Price,ImageUrl) VALUES ("Laptop","100","c-1.png"),("Drone","200","c-2.png"),("VR","300","c-3.png"),("Tablet","50","c-5.png"),("Watch","90","c-6.png"),("Phone Covers","20","c-7.png"),("Phone","80","c-8.png"),("Laptop","150","c-4.png");

EOF

sudo mysql < db-load-script.sql

mysql_db_results=$(sudo mysql -e "use ecomdb; select * from products;")

if [[ $mysql_db_results == *Laptop* ]]
then
  print_color "green" "Inventory data loaded into MySQl"
else
  print_color "green" "Inventory data not loaded into MySQl"
  exit 1
fi


print_color "green" "---------------- Setup Database Server - Finished ------------------"

print_color "green" "---------------- Setup Web Server ------------------"

# Install web server packages
print_color "green" "Installing Web Server Packages .."
sudo yum install -y httpd php php-mysqlnd

# Configure firewalld rules
print_color "green" "Configuring FirewallD rules.."
sudo firewall-cmd --permanent --zone=public --add-port=80/tcp
sudo firewall-cmd --reload

is_firewalld_rule_configured 80

# Update index.php
sudo sed -i 's/index.html/index.php/g' /etc/httpd/conf/httpd.conf

# Start httpd service
print_color "green" "Start httpd service.."
sudo systemctl  start httpd
sudo systemctl enable httpd

# Check FirewallD Service is running
check_service_status httpd

# Download code
print_color "green" "Install GIT.."
sudo yum install -y git
sudo git clone https://github.com/kodekloudhub/learning-app-ecommerce.git /var/www/html/
sudo sed -i 's#// \(.*mysqli_connect.*\)#\1#' /var/www/html/index.php
sudo sed -i 's#// \(\$link = mysqli_connect(.*172\.20\.1\.101.*\)#\1#; s#^\(\s*\)\(\$link = mysqli_connect(\$dbHost, \$dbUser, \$dbPassword, \$dbName);\)#\1// \2#' /var/www/html/index.php

print_color "green" "Updating index.php.."
sudo sed -i 's/172.20.1.101/localhost/g' /var/www/html/index.php

print_color "green" "---------------- Setup Web Server - Finished ------------------"

# Test Script
web_page=$(curl http://localhost)

for item in Laptop Drone VR Watch Phone
do
  check_item "$web_page" $item
done

Save the file with an extension .sh i named it deploy-ecom-app.sh

Try it out and lemme know if it works for you :) Thanks guys, see you on the next one.

Comming back to this project... Still on the foundamentals

tundek — Wed, 01 Jan 2025 08:41:04 +0000

🚀 Learning by Doing: Building an Incident Alert System 🛠️

Serdar Shefketov ・ Dec 23 '24

#go #kafka #microservices #kubernetes

Making docker available in Jenkins without a plugin. Part 1

tundek — Sat, 24 Feb 2024 17:10:42 +0000

In this article, you will be able to run all your favourite docker commands in the same container that has your jenkins running..

If you already have Jenkins running in a container, we will stop the container and restart it with the following commands.

Step 1: Check the status of the running container

docker ps

run the command docker stop 8cb594e942c2 to stop the container. Once the container stops, we can now re-run our jenkins app with this command

docker run -p 8080:8080 -p 50000:50000 -d -v jenkins_home:/var/jenkins_home -v /var/run/docker.sock:/var/run/docker.sock -v $(which docker):/usr/bin/docker jenkins:jenkins:lts

Yeah, i know :), the command seems ambiguous, complex to understand and confusing, let's break it down.

docker run: This is the command to create and start a new Docker container.
-p 8080:8080: This option maps port 8080 of the host to port 8080 of the container. Jenkins typically runs its web interface on port 8080, so this mapping allows you to access the Jenkins web interface through your host machine's port 8080.
-p 50000:50000: This maps port 50000 of the host to port 50000 of the container. Jenkins uses this port for agent connections, allowing build agents to communicate with the Jenkins server.
-d: This option runs the container in detached mode, meaning the container runs in the background and does not block the terminal session.
-v jenkins_home:/var/jenkins_home: This mounts a volume named jenkins_home to /var/jenkins_home inside the container. /var/jenkins_home is the default directory Jenkins uses to store its configuration and data. By mounting a volume, you ensure that this data persists across container restarts and recreations, maintaining your Jenkins state.
-v /var/run/docker.sock:/var/run/docker.sock: This volume mount is particularly interesting. It mounts the Docker socket from the host into the container. This allows the Jenkins container to communicate with the Docker daemon of the host machine, effectively allowing Jenkins to launch other Docker containers. This is often used for running Jenkins jobs inside separate Docker containers.
-v $(which docker):/usr/bin/docker: This mounts the Docker binary from the host into the container at /usr/bin/docker. This allows Jenkins running inside the container to execute Docker commands directly, assuming Docker is installed on the host at the path returned by $(which docker).
jenkins:jenkins:lts: This specifies the Docker image to use. It seems like there's a repetition in the image name; typically, it would be something like jenkins/jenkins:lts where jenkins/jenkins is the Docker Hub repository for Jenkins images, and lts specifies that you want to use the Long-Term Support version of Jenkins.

Let's login into the Jenkins container

docker exec -it 8cb594e942c2 /bin/bash

If we try to execute the command docker pull redis on the container, we will get an error which needs to be corrected so that we can successfully run docker commands on the container.

Exit from the shell and login as root

docker exec -it -u 0 8cb594e942c2 /bin/bash

follow the above command with the following

chmod 666 /var/run/docker.sock
ls -l /var/run/docker.sock

With the above, you are now able to execute docker commands on the jenkins execute shell.

Step 2: Build a docker image for our App

To build the docker image, we will now go into Jenkins and add the following command on the Execute shell part using the Dockerfile to build the image

docker build -t java-maven-app:1.0 .

Step 3: Pushing the image to Artifactory (Docker Repository)

We will now be pushing the image we have created into a private repository (docker repo) in this case.

Some of the configurations we need to do on Jenkins include the following

After a successful build on Jenkins we will have an output like so with a SUCCESS message

And the image will be pushed to the private repo

Setting up Ansible for Automating tasks

tundek — Sat, 18 Nov 2023 06:19:07 +0000

Setting up Ansible

Hey Fellas, in this article, we will be installing Ansible and creating a simple task of automation using Ansible and showing you all the processes involved.

We need to create 3 Amazon EC2 instances, 1 will be the Master while the other 2 will be the targets.

After creating the Instances, we can name one of them Ansible_Master while the other two Ansible_Target1 and Ansible_Target2 to simulate.

Step 1: Install Ansible

With the following command, we can install ansible

sudo yum install ansible

Create the ec2-key.pem file and paste your key into this file

It should look something like this if you run the cat ec2-file.pem

Run chmod on the key file to ensure it is not accessible to anyone and only the root user can read the file.

chmod 400 ec2-file.pem

The image below shows how to use Ansible to call different servers all at the same time

Step 2: Create Inventory File

Use the nano program to create the inventory.txt file

nano inventory.txt

ansible-target-1 ansible_host=16.170.230.179 ansible_connection=ssh ansible_user=ec2-user
ansible-target-2 ansible_host=51.20.116.72 ansible_connection=ssh ansible_user=ec2-user

Escape and save the file. To run the file, we can use the following

ansible ansible-target-1 -m ping -i inventory.txt

We should get this error and i will explain in a sec why that is

In the inventory.txt file the mode of connection we used is SSH and we need the SSH key for the servers we are trying to connect to, that is why we are receiving this error resposne from the server.

We need to assign the SSH key we copied at the beginning when installing our instances to the ssh-agent using the command below

ssh-agent bash
cp ec2-key.pem ~/.ssh/
ssh-add ~/.ssh/ec2-key.pem

Running this command again

ansible ansible-target-1 -m ping -i inventory.txt

ansible ansible-target-2 -m ping -i inventory.txt

To ensure that we can connect to our servers (instances) at all times, we need to configure the ansible configuration file to allow us to do that without interruption.

If the ansible config file does not exist in the /etc/ansible/ansible.cfg we can create it by running the following

ansible-config init --disabled -f ini > /tmp/ansible.cfg

The config file will be sent to the /tmp/ansible.cfg (tmp folder) and then it can be moved to the main folder /etc/ansible

As a refresher, we can use

sudo cp /tmp/ansible.cfg /etc/ansible

to copy the ansible config file into the main directory where it can be read.

Let's now try the command once again for both targets

ansible ansible-target-1 -m ping -i inventory.txt

ansible ansible-target-2 -m ping -i inventory.txt

Assuming we are having a hundred or more targets, do we keep changing the targets number using the above command? NO

Here is a better way to ensure we can communicate to all the targets at once:

Let's add a tag-name servers to the inventory.txt file we created earlier.

Your inventory.txt file should now look like this

Run this command to see the magic all targets can now be connected to at the same time with a single command

ansible servers -m ping -i inventory.txt

IMPLEMENTATION OF the LEMP STACK on AWS

tundek — Sun, 01 Oct 2023 14:40:23 +0000

WEBSTACK: IMPLEMENTATION OF the LEMP STACK on AWS

The LEMP stack is a collection of open source and free software bundles which web developers around the world use to write software of different types and application. Where the accronym L stands for the Linux operating system, E is the Nginx server the most popular server software, M stands for MYSQL (Also one of the most popular Database server) and P for PHP backend programming languauge.

Pre-requisites for Installing Nginx server.

Step 0:

For this project, it is better to use a differnet AWS instance. Kindly create a new one, which by now you already know how todo.
Once it has been installed and .pem key download, navigate into the directory housing the key and SSH into the server.
Also please make sure you have port 80 active on the instance for this project.

Installing Nginx Web Server

update a list of packages in package manager and install nginx

sudo apt update
sudo apt install nginx

Command output

To verify and test that Nginx has been successfully installed and working, copy and paste the following code

sudo systemctl status nginx

Command output

Let us check how we can access our server locally on our Ubuntu shell using

curl localhost:80 
curl http://127.0.0.1:80

We can now check the result on our browser and see if the server displays th following information, if it does, then Nginx worked using the http://:80
replacing the with the IP address from your provider in this case AWS.

You can get your public address information on the AWS panel or use the command

curl -s http://169.254.169.254/latest/meta-data/public-ipv4

Command output

Installing MySQL

Step 2: Installing MySQL on the server

We now have a Webserver, but for a complete application, we also need to store information and data, so we need a DataBase Management System (DBMS) to help with this, in this case MySQL

Let's install MySQL on our server

sudo apt install mysql-server

Use the command below to log into the Database Admnistation as user root. Right now our Database is not secure and anyone can have access by just typing the command below.

sudo mysql

Output

Let us firstly secure the Database by running the secure default script to lock anyone that tries to have access with the command below.

ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'PassWord.1';

Output

If you try to login now, except as root. It is time to start the interactive script for securing the DB.

sudo mysql_secure_installation

Output

Installing PHP

Step 3: Installing PHP on the server

We now have Nginx and MySQL installed on our server. But we still need a server side language to complete the STACK, since we want a LEMP STACK application it will be imcomplete without the server side programming Language in this case PHP

Let's install PHP now. Paste the command below on your terminal

sudo apt install php-fpm php-mysql

Output

Use the command php -v to check the version of PHP installed or if PHP is already installed

php -v

Output

At this point, our LEMP STACK has now been completed, Linux, Nginx, MySQL, PHP (LEMP)

Configuring Nginx to use PHP Processor

Step 4: Configuring Nginx to use PHP Processor on the server

Similar to Apache's virtual host (Refresher: Allows you host more than one website on the server), Nginx has a server block(s) that encapsulate configuration details allowing you to host multiple website on a single server.

Nginx has one server block by default and servers the default directory /var/www/html. This works well for a single website, however for multiple websites, we might need to make use of the /sites-available diretory similar to that of Apache.

We need to create a directory in the /var/www folder and do the configuration settings.

Let's create a new project "projectLEMP" in the /www/ folder

sudo mkdir /var/www/projectLEMP

We will now assign the ownership of the directory with the $USER environment variable to the current user

sudo chown -R $USER:$USER /var/www/projectLEMP

Next is to open a new configuration file in the sites-available directory of the

sudo vi /etc/nginx/sites-available/projectLEMP

Then copy and paste the following in the open file above and save the file when done.

#/etc/nginx/sites-available/projectLEMP

server {
    listen 80;
    server_name projectLEMP www.projectLEMP;
    root /var/www/projectLEMP;

    index index.html index.htm index.php;

    location / {
        try_files $uri $uri/ =404;
    }

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/var/run/php/php8.1-fpm.sock;
     }

    location ~ /\.ht {
        deny all;
    }

}

Let's take out time to understand what each of the lines above mean

listen: This tells the server what port to listen on, port 80 which is the default for HTTP

root: This defines the default document root that contains all the website files

index: Defines the order in which Nginx will priortize the index files. Common practise ensure index.html has more precedence than index.php file

servername: Indicates which domain name and/ IP address the server block should point to

location / : The first location block includes a try_files directives and then it checks for existence of files or directories matching the URI request. If Nginx doesn't find the files it returns a 404 error

location ~ .php$ : The location block does the actual PHP processing by pointing Nginx to the fastcgi-php.conf configuration file, and the php8.1-fpm.sock file which declares what sock is associated with the php-fpm

location ~ /.ht : This location is the last one that deals with the .htaccess file which Nginx does not process.
By adding the deny all if any .htaccess file finds it's way

Let's activate the configuration we just did by linking the config file from Nginx's sites-enabled directory.

sudo ln -s /etc/nginx/sites-available/projectLEMP /etc/nginx/sites-enabled/

Output

The above comand tells Nginx to use the projectLEMP config file when next it is loading.

Checking to see if there are any errors

sudo nginx -t

Output

The above output result shows that the configuration is fine and good to go.

Next is to disable the default Nginx config file currently listening on port 80, to do this, run

sudo unlink /etc/nginx/sites-enabled/default

Let's reload nginx for the changes to take effect

sudo systemctl reload nginx

We can run this code to create a sample index.html file which displays the hostname and public IP address of the server.

sudo echo 'Hello LEMP from hostname' $(curl -s http://169.254.169.254/latest/meta-data/public-hostname) 'with public IP' $(curl -s http://169.254.169.254/latest/meta-data/public-ipv4) > /var/www/projectLEMP/index.html

Output

Testing PHP with Nginx

Step 5: Testing PHP with the Nginx server

We will be writing a very basic php information file. Use the nano /var/www/projectLEMP/info.php and paste the following code

<?php
phpinfo();

Output

Always ensure you remove the php info file from the server using sudo rm /var/www/projectLEMP/info.php command.

Retrieving data from MySQL database

Step 6: Writing code to retrieve data from the MySQL DB

Let us create a simple todo list application, first the database.

sudo mysql

Then, create a database using the following command

create database TODO;

show databases;

Output

Next is to create a user that will have access or priviledges to the database we just created. We are defining the user 'afeez_user' and password -> 'Password1' using this command

CREATE USER 'afeez_user'@'%' IDENTIFIED WITH mysql_native_password BY 'PassWord.1';

After this, let's grant permission to the user afeez_user to

Output

GRANT ALL ON TODO.* TO 'afeez_user'@'%';

The above command will allow 'afeez_user' full priviledge to work on the TODO database while preventing the user from modifying or creating other databases on the server.

CREATE TABLE TODO.todo_list (item_id INT AUTO_INCREMENT,content VARCHAR(255),PRIMARY KEY(item_id));

Adding some sample data into the table todo_list

INSERT INTO TODO.todo_list (content) VALUES ("My first important item");
INSERT INTO TODO.todo_list (content) VALUES ("My second important item");
INSERT INTO TODO.todo_list (content) VALUES ("My third important item");
INSERT INTO TODO.todo_list (content) VALUES ("One more important item");

SELECT * FROM TODO.todo_list;

Output

It is time to now create a file a php file to access the databse we just created and pull the record to be displayed on the browser.

<?php
$user = "afeez_user";
$password = "PassWord.1";
$database = "TODO";
$table = "todo_list";

try {
  $db = new PDO("mysql:host=localhost;dbname=$database", $user, $password);
  echo "<h2>TODO</h2><ol>";
  foreach($db->query("SELECT content FROM $table") as $row) {
    echo "<li>" . $row['content'] . "</li>";
  }
  echo "</ol>";
} catch (PDOException $e) {
    print "Error!: " . $e->getMessage() . "<br/>";
    die();
}

Output

Installing Webstack, LAMP(Linux, Apache, MySQL and PHP) on AWS instance

tundek — Wed, 27 Sep 2023 13:36:03 +0000

WEBSTACK: IMPLEMENTATION OF the LAMP STACK on AWS

The LAMP stack is a collection of open source and free software bundles which by web developers around the world use to write software of different types and application. Where the accronym L stands for the Linux operating system, A is the Apache server the most popular server software, M stands for MYSQL (Also one of the most popular Database server) and P for PHP backend programming languauge.

Pre-requisites for Installing Apache server.

Step 0:

Installed an E2C instance and SSH into the server

Installing Apache and Updating the Firewall

Apache HTTP Server is one of the most used servers in the world. More than 60% of the world's server is Apache. Most especially web developers use this server because it is simple to setup and open source. Ther are other servers which are also in use like IIS by Microsoft, Nginx

Use the code below to install Apache on your AWS instance

update a list of packages in package manager

sudo apt update

Command output

Step 1: Installing Apache server

run apache2 package installation

sudo apt install apache2

Output

Run the command below to verify that Apache is running fine

sudo systemctl status apache2

Output

The status indicates Active: running => showing that the apache server is now running, and we can test with the following commands which will dipsplay the content of the server file

Use the command

curl http://localhost:80

curl http://127.0.0.1:80

localhost:80 indicates that we are calling the local DNS server to to display the content of the server, while 127.0.0.1:80 is using the IP address of the server to check the details of the server.
We are using port 80, which is HTTP for web servers

Checking if Apache Server is working using our IPv4 (from AWS instance) on the browser

Visit your browser and type:
http://:80

Output

Use the curl command below to check your Public IP address without going to the AWS console

curl -s http://169.254.169.254/latest/meta-data/public-ipv4

Output

Installing MySQL

Step 2: Installing MySQL on the server

We now have a Webserver, but for a complete application, we also need to store information and data, so we need a DataBase Management System (DBMS) to help with this, in this case MySQL

Let's install MySQL on our server

sudo apt install mysql-server

Use the command below to log into the Database Admnistation as user root. Right now our Database is not secure and anyone can have access by just typing the command below.

sudo mysql

Output

Let us firstly secure the Database by running the secure default script to lock anyone that tries to have access with the command below.

ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'PassWord.1';

Output

If you try to login now, except as root. It is time to start the interactive script for securing the DB.

sudo mysql_secure_installation

Output

Installing PHP

Step 3: Installing PHP on the server

We now have Apache and MySQL installed on our server. But we still need a server side language to complete the STACK, since we want a LAMP STACK application it will be imcomplete without the server side programming Language in this case PHP

Let's install PHP now. Paste the command below on your terminal

sudo apt install php libapache2-mod-php php-mysql

Output

Use the command php -v to check the version of PHP installed or if PHP is already installed

php -v

Output

At this point, our LAMP STACK has now been completed, Linux, Apache, MySQL, PHP (LAMP)

NOTE: You can check the configuration of VirtualHost (VHosts) on the server. ==> VIRTUAL HOST

Also use TO check the configuration of your server

apachectl -S

Creating a virtual Host for your Website Using Apache

Step 4: Creating a Virtual Host (VHost) using Apache Server fro hosting your website

In this project we will be using a domain name called projectlamp, but ofcourse you can have anyname of your choice.

By default document root that serve the website are on the directory /var/www/html which comes with apache on Ubuntu 2X.X.X

Let us create our project folder using the project name by navigating into the folder /var/www/ and create projectlamb directory

or we can use the command

sudo mkdir /var/www/projectlamp

Also use the command

sudo chown -R $USER:$USER /var/www/projectlamp

to assign ownership of the folder to the current user.

Let's open and create a new configuration file for the sites-available directory.

sudo vi /etc/apache2/sites-available/projectlamp.conf

This command will open and create an empty file projectlamp.conf which will host the info below

use the i insert mode, then paste the code below

And add the following line of code in the projectlamp.conf file

<VirtualHost *:80>
    ServerName projectlamp
    ServerAlias www.projectlamp 
    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/projectlamp
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

then :wq! then press enter to save

Let us check the content of the sites-available directory the directory should now have the projectlamp.conf

Summary: With the above Virtual Host Config, we are now saying Apache should server projectlamp using the /var/www/projectlamp as it's root directory.

You can comment out the first 2 lines (ServerName & Server Alias) if you don't want to use domain name to access the server using the # symbol.

Let's now enable the new virtual host by running the command

sudo a2ensite projectlamp

Fun fact, i think the meaning of a2ensite could be "Apache2 enable Site (a2ensite)" | Or what do you think?, that makes sense to me

Anyway, remember we checked the content of the sites-available directory we saw a file name 000-default.conf, we need to disable this file because it is responsible for displaying the default files that comes pre-installed on Apache2.

Use the command

sudo a2dissite 000-default

We also need to run the command to ensure there are no config issues if we get the result Syntax OK then everything looks good.

sudo apache2ctl configtest

Finally, let's reload the apache server

sudo systemctl reload apache2

Enable PHP on the Website

Step 5: Enabling PHP on the website

Apache by default looks for the index.html file on the server called Directoryindex, this is the file that get called/executed when the directory is called to server the pages hosted in it.

Even though we might have an index.php file, the index.html will get called first by default, which can be used during maintainance mode to inform the users what is going on.

To change the defualt behaviour of the Directoryindex, we need to edit the file /etc/apache2/mods-enabled/dir.conf

run the command below:

sudo vim /etc/apache2/mods-enabled/dir.conf

<IfModule mod_dir.c>
        DirectoryIndex index.html index.cgi index.pl index.php index.xhtml index.htm
</IfModule>

Output

After editing the file, you can save & close the file then restart apache server to effect changes

sudo systemctl reload apache2

sudo echo 'Hello LAMP from hostname' $(curl -s http://169.254.169.254/latest/meta-data/public-hostname) 'with public IP' $(curl -s http://169.254.169.254/latest/meta-data/public-ipv4) > /var/www/projectlamp/index.html

We can use the above code to create an index.html file in teh /var/www/projectlamp directory to test our server.

Output

And BOOM!!! Congratulatios, We have our first website hosted on AWS

Introduction to GIT and GitHUB

tundek — Thu, 21 Sep 2023 19:01:21 +0000

Initializing a Repository and Making Commits

First off, when you are trying to make use of git, there are some general setup that needs to be cleared off before we start using git on our working environment.

But before then, we should have git installed on our PCs

After installation of git, then we can use this setting to setup our git configuration

First thing, we initialize git on our working directory

git init

Code Output

Then we can go ahead with our setup. You can change the information as required to your details

    git config --global user.name "Afeez"
    git config --global user.email "tundek79@gmail.com"
    git config --global init.defaultBranch main

The above command will

Create a username
Create an email for the account
create a default branch called main

Making commits

First, we need to track our working files by adding the files into the staging area before comming them.

There are 3 different stages where files are in the GIT lifecycle

Working files (These are the files that you are currently working on and has not been tracked by GIT)
Staging (At this stage, the files are already been tracked by GIT but has not been saved)
Commit (At this point the files are now saved into the history books (if you will))

Here's the demonstration for the above

From the above image, i used the git status to check the current status of my files on GIT and it indicates that none of the files are being tracked since i initialized git on the working folder.

This id also indicated with the red color of al files that are yet to be tracked.

I ran another command git add . command to start tracking all the files in the directory.

After running the git add command followed by the git status, the above is the result, showing a green color of all the working files indicating the files are now being tracked and once work is done, can be commited.

Let's commit the changes into the history books using the command

git commit -m "first commit"

Code Output

Working with Branches

It's good that we now able to make commits and save into the history book which doesn't really go away unless maybe you or someone else tear (delete) the history book, but not sure anyone will do that nowadays.

Anyway, let's say we have a project already in production and our customers are enjoying, but we need to add a new feature or work on an existing feature. How do we go about this without running into issues with our customers complaining they are unabel to use our softwares.

A concept of branches came onboard, where by we create an exact copy of our project and we can make edits as required. It might be working on a new or existing feature. After working, testing and making sure all is fine with our new version, then we merge to the main branch. Enough talking, let's get working

Creating a new branch

With what i have seen (abi), there seems to be a number of ways to creating a new branch. Let's explore some of them.

git branch my_new_branch

The above creates a new branch but doesn't login to it

To create and switch into a new branch, use

git switch -c another_branch

Code output

Another method of creating branch, using the checkout command and listing the branch

Use can also the use the command

git checkout -b newest_branch

and use

git branch

`
to check the list of all available branches

Code output

Change into an Old branch

To change your current branch into an old one, use the command

git checkout <branch-name> OR git swith <branch-name>

Example:

Code output

Switch =>

Checkout =>

Mergin a Branch into another Branch

Let's switch into a new branch and make some changes on the new branch we switch to. Then exit into the main branch and see if the changes effect on the main branch

git switch new-branch

Make some edits on the new branch, commit the changes and switch back into the main branch then run the following commands

git merge -m "Merging sample file, into the main branch" new-branch

Code output

Collaboration and Remote Repositories

We have been working on our local computer or local server all these while, when we want to collaborate with other developers or team mates, they might not have access to our local computer, which is why it is important to work remotely and collaborate from their.

For Creating Remote repositories, we will be using GitHub as a Social Coding platform where repositories can be created, worked on.

The account creation for github should be fairly simple to do, visit the GitHub Website
After that, create a repository where all your files will be hosted and let's connect to the repo and upload all the work we have done so that we can collaborate with our workmates.

First off, we need to add a remote reporsitory to the local repo we have been working on, use the command

git remote add origin https://github.com/tundek/DevOps.git

Afterwards, it is time to push all your files to the remote repository using the command

git push origin <branch-name> => git push origin main

Branch Management and Tagging

Introduction to Markdown Syntax

Sys Admin: How to configure sudoers file, Admin privileges.

tundek — Sun, 10 Sep 2023 16:35:09 +0000

Hi guys, hope you are doing are doing well. I'm excited to share another piece of informative writeup today.

In this article I will be showing you some basic but useful configurations commands which includes configuring the sudoers file, admin rights, group right etc.

Configuring the Sudoers file

Have you seen this error message before when trying to run a sudo command even if you installed the linux O.S yourself on your PC or when you install Linux on VM machines.

The above image is showing us that the user "afeez" cannot use the sudo command which mean user afeez cannot perform elevated tasks using sudo.

How do we fix this?

There are numerous ways of fixing this issue. But we will go with the most common solution, that is we can

Add the user into the sudoers file with all Admin privileges.

But there is a problem with this solution...

Let's say we have about 10 new users that needs to have an admin privilege, that means we have to keep doing this. Editing the sudoers file for every user. Which will definitely waste our time and above all, not smart at all.

Create groups and add each user(s) with the similar tasks to the same group. Sounds smart enough??

Lemme show you how to do this.

Let us create a group called devZ, we will give it all the access we require to run sudo then add user afeez to the group.

sudo groupadd devZ

Yeah, you guessed it. It throws an error, because we still need sudo to create a new user.

So, the workaround is to enter the command

su (su = switch user => $ )you will see the $ prompt once you have gained that access.

followed by your password then we can continue with our solution. Just wanted to throw that in, incase you encounter such issue. You are welcome :)

then run the groupadd command to create a group and add the user afeez to be a part of the group.

sudo usermod -a -G genZ afeez

The above command will add user afeez into the genZ group

You can confirm this by running the command id afeez

Step 2:

Let's now edit the sudoers file.

All configuration files can be found in the /etc/ folder, the sudoers file is in the /etc/sudoers

Use the

sudo visudo /etc/sudoers

command to open the sudoers file and lemme quickly go through the output

*All line starting with # represents comments. (Not executed by the shell)

root ALL=(ALL:ALL)ALL - this mean that the root user has unlimited privileges and can run any command
%admin ALL=(ALL)ALL - All % specifies a group, which mean anyone in the admin group has the same privilege as d root user.
%sudo ALL=(ALL:ALL) ALL - All users in the sudo group have the same privileges as the root user and can run any command.

I added the group devZ under the %sudo with the line

%genZ ALL=(ALL:ALL) ALL

then save the file, depending on the editor you are using.

Another trick to know if your config file save successfully without any errors, use command

sudo visudo -c

We need to confirm the file is OK, this is because it has permissions configuration which if mis-configured could log you completely and not have access to your server AGAIN. You want to be very careful with these configuration files.

You need to reboot the system then try the sudo command again.

reboot now

Apply the exit command to take you back into the user, in this case afeez and try the sudo commands again

And BOOM! we now have access to the sudo command.

I hope this helps.

Thanks for reading :)

How to connect to a remote server securely using Open SSH (Secure SHell)

tundek — Sat, 09 Sep 2023 10:37:54 +0000

In this article i will be explaining how we can connect to a remote server using the Open SSH (Secured Shell) protocol.

But before that, we will be getting some basic command checks out of the way.

First, we check the client PC to ensure the SSH directory is currently empty.

ls -latr ~/.ssh

Output

Step 1:

Generate the SSH key pair (SSH used the asymmetric cypher for encryption)

sudo ssh-keygen

Output

If you noticed the above image, the SSH key pair was created in the /root/.ssh/ directory.

Checking the directory to see the files generated.

sudo ls -ltar /root/.ssh

Output

We are done with the client Configuration, SSH on the client has now been installed

On to the Server now

Step 2:

Install the Open SSH Server software on the Server itself.

sudo apt install openssh-server -y

Step 3:

Now we need to send/transfer the public key on the client computer to the Server using the command (utility tool on the client ssh) on the client:

sudo ssh-copy-id -i /root/.ssh/id_rsa.pub username@serverIPAddress

sudo ssh-copy-id -i /root/.ssh/id_rsa.pub afeez@192.168.1.163

You can use the ifconfig command to check the IP address of the server

The public key will now be transferred into the server.

To confirm this, run the command on the server.

ls -ltar ~/.ssh

Output

To confirm the public key is the same you can run a cat command on both files

Final Step:

Connect to the remote server using the command:

ssh username@remoteserverIP

ssh afeez@192.168.1.163

Output

And BOOM!!!!

We are now connected to the Sever using SSH.

I hope this helps.