<?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 Janella Baker on Medium]]></title>
        <description><![CDATA[Stories by Janella Baker on Medium]]></description>
        <link>https://medium.com/@janella.baker?source=rss-ba6f93f384af------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*144ahhyMRMhI0pPt6kVt5A.jpeg</url>
            <title>Stories by Janella Baker on Medium</title>
            <link>https://medium.com/@janella.baker?source=rss-ba6f93f384af------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:43:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@janella.baker/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[Creation of an Auto Scaling Group of EC2 instances]]></title>
            <link>https://medium.com/@janella.baker/creation-of-an-auto-scaling-group-of-ec2-instances-f81ec1365ed2?source=rss-ba6f93f384af------2</link>
            <guid isPermaLink="false">https://medium.com/p/f81ec1365ed2</guid>
            <category><![CDATA[ec2]]></category>
            <category><![CDATA[vpc]]></category>
            <category><![CDATA[application-load-balancer]]></category>
            <category><![CDATA[high-availability]]></category>
            <category><![CDATA[auto-scaling-groups]]></category>
            <dc:creator><![CDATA[Janella Baker]]></dc:creator>
            <pubDate>Sun, 26 Jun 2022 13:45:38 GMT</pubDate>
            <atom:updated>2022-06-26T13:45:38.263Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello reader. I hope this article helps you to understand some of the AWS services that can be used together to provide a solution for yourself or for a business. Just think of the EC2s as servers in your private cloud or at an organization for whom you work, and you need to spin up three servers in different Availability Zones for high availability. We’ll load those 3 EC2s into an Auto Scaling Group so that if one server goes down, another server will spin up automatically. We’ll also use an Application Load Balancer to help with traffic distribution to the EC2s. There is a whole lot more to learn from this article so let’s get started!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/865/1*F-J78EzI99cUSHI_tQSntA.png" /><figcaption>Reference Architecture</figcaption></figure><p><strong><em>Requirements:</em></strong> AWS Management Console Access and Internet connection</p><p>First things first, we need to create a custom Virtual Private Cloud (VPC) for all of this to take place in.</p><p>From the AWS Management Console, search for VPC in the search box and click <strong>VPC</strong>. Then click <strong>Create VPC </strong>in the upper right corner.</p><p>We are going to use the <strong>VPC and more</strong> option so that we can create three customized public subnets in different availability zones while creating our VPC at the same time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*Os64ZZQX66hOT05BSUM9hA.png" /><figcaption>VPC and more</figcaption></figure><p>Name your VPC, provide the IPv4 CIDR block, select 3 availability zones for high availability (HA) and scroll down to the bottom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/345/1*2u7oGUVNU61ut-fCjPLK5w.png" /><figcaption>VPC settings</figcaption></figure><p>Select 3 public subnets, 0 private subnets, and click <strong>Customize subnet CIDR blocks</strong> as shown above. Doing this gives us the option to give our Public Subnets the IP addresses that we choose. We can leave the rest of the defaults and click <strong>Create VPC</strong>.</p><p>Now it is time to create an Auto Scaling Group (ASG). From the AWS Management Console navigate to <strong>EC2</strong> and select <strong>Auto Scaling Groups</strong>. We will use the <strong>Launch Template</strong> option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*AEs4pWY5kcweXrR2azuOFA.png" /><figcaption>Name your Auto Scaling Group</figcaption></figure><p>Click, <strong>create a launch template</strong> under Launch Template.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/621/1*CHeiliYE-JTXHebjWN8Lkw.png" /><figcaption>Launch Template</figcaption></figure><p>Name your launch template (use dashes as needed in the name), add a description, and select the check mark to provide guidance as shown above.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*jpxftkdBz9PzlTpDpBIICQ.png" /><figcaption>Launch template options</figcaption></figure><p>From the launch options menu, select the new VPC and the three public subnets that were just created as shown above.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/1*d0S5LKbA6Abl9hX1s31sxA.png" /><figcaption>Launch template- OS</figcaption></figure><p>Select Amazon Linux 2 AMI as it is Free tier eligible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/615/1*0TVmGUGL2hZeSR8rVYVY9w.png" /><figcaption>Launch template- Instance type and key pair</figcaption></figure><p>From here, we will use the Free tier eligible <strong>t2.micro</strong> instance type. You should also use a key pair to securely log into your EC2s if necessary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/609/1*vlmLsmBy_6HxzEcxmEsfuA.png" /><figcaption>Launch template- network and security</figcaption></figure><p>At this section, click <strong>Create security group</strong>, name your security group, add a description, and select the new custom VPC that was just created as shown above.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/1*KH2laI1YjUOe74_fl_Hy3A.png" /><figcaption>Launch Template- security group</figcaption></figure><p>We need to configure rules for our new security group. Here, we’ll add two inbound security group rules. One is for SSH on port 22 (to securely connect to your instances) and one is for HTTP on port 80 (to connect to the public IP of your EC2 running Apache).</p><p>IMPORTANT: Choose <strong>My IP</strong> for the Source type (not custom) for SSH. That way, only your IP address will be allowed to SSH into your EC2s.</p><p>Scroll down to open the <strong>Advanced network configuration</strong> tab so we can add a network interface and auto-assign a public IP address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/1*B_xtOyGJeoGhVfcIP3Uw0A.png" /><figcaption>Choose Enable from the Auto-assign public IP dropdown</figcaption></figure><p>Scroll down some more to <strong>Advanced details</strong> so that we can add a small bash script to the template.</p><p>All the way down at the bottom of the template, there is a field for us to load our script. Copy and paste the below script into the <strong>User data</strong> field as shown below. This will allow all of our EC2s to spin up with Apache already installed and enabled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/445/1*htILSIc7KG8RALY7vWwsFg.png" /><figcaption>Script to install Apache</figcaption></figure><p>Now navigate back to the EC2 menu so we can create an Application Load Balancer (ALB). Here, we will create the ALB to help distribute web traffic to our EC2s.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/160/1*G7-n92gDA070sIJQQoI1bA.png" /><figcaption>Select Load Balancers</figcaption></figure><p>Click <strong>Load Balancers</strong> on the left menu as shown above and then click <strong>Create Load Balancer</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*doSMiMNifJJNWEsbBMuTQw.png" /><figcaption>ALB creation</figcaption></figure><p>Select <strong>Attach to a new load balancer</strong>, ALB, name your ALB (with dashes if necessary) and select <strong>Internet-facing</strong> as shown above.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*z9vaAx55OHDEiNOTTyThSA.png" /><figcaption>ALB creation continued</figcaption></figure><p>Scroll down and you should see the three availability zones already selected for us. Here will will create a target group. Create a name for your target group under the <strong>New target group name </strong>field as shown above.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*NpupQlfhJJ-GeMr5GVl0Sg.png" /><figcaption>ALB creation continued</figcaption></figure><p>The <strong>Health checks</strong> option is optional as it states but here we will accept the default health check grace period of 300 seconds and select the box to <strong>Enable group metrics collection within CloudWatch</strong>.</p><p>Next, we will move on to configure group size and scaling policies:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/1*r23PYMd6t3oiZEgQhk-o_A.png" /><figcaption>Group size and scaling policies</figcaption></figure><p>Here, we will select 3 for <strong>Desired capacity</strong>, 2 for <strong>Minimum capacity</strong>, and 5 for <strong>Maximum capacity</strong> as shown above. This is referring to the number of EC2s that we need before an action, such as spinning up a new EC2 after one fails, will occur. We will also select the <strong>Target tracking scaling policy </strong>radio button, create a policy name, select the metric and target value as shown above.</p><p>Click <strong>Next</strong> and we can skip notifications, tags, and go to <strong>Review</strong>. Click <strong>Create Auto Scaling Group.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*b61TROdidvc6dPZSZ4Je2g.png" /><figcaption>ASG provisioning</figcaption></figure><p>We’ll quickly hop over to peek at our EC2s to see if they are coming up. Navigate to the <strong>EC2</strong> menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*u4_wGrgZU4-rVQb0yLY8XQ.png" /><figcaption>Three EC2s provisioning</figcaption></figure><blockquote>Yaaaay, EC2s are coming up!!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*4eQHPxk2u6O1bdJFjdPEPQ.png" /><figcaption>Three EC2s running</figcaption></figure><p>Now that all 3 EC2s are<strong> Running</strong>, we can pick one of them, grab the public IP and navigate to it from a web browser. <br>*Be sure to use HTTP in your browser*</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*veteAjotO1lemILg4b2jnw.png" /><figcaption>Apache banner</figcaption></figure><p>If you got the above banner, you did <strong><em>A LOT</em></strong> so pat yourself on the back. Haha</p><p>Stay tuned for Part 2 because we will add a stress tester so we can bring down an EC2 with say, high CPU utilization, monitor it on CloudWatch, and have the ASG bring an instance back up for us auto-magically 😊</p><p>Thanks for stopping by!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f81ec1365ed2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating an EC2 instance with a web server (simultaneously)]]></title>
            <link>https://medium.com/@janella.baker/creating-an-ec2-instance-with-a-web-server-simultaneously-b4b8a575d427?source=rss-ba6f93f384af------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4b8a575d427</guid>
            <category><![CDATA[apache]]></category>
            <category><![CDATA[ssh]]></category>
            <category><![CDATA[bash]]></category>
            <category><![CDATA[ec2]]></category>
            <category><![CDATA[web-server]]></category>
            <dc:creator><![CDATA[Janella Baker]]></dc:creator>
            <pubDate>Mon, 13 Jun 2022 15:13:39 GMT</pubDate>
            <atom:updated>2022-06-13T15:13:39.354Z</atom:updated>
            <content:encoded><![CDATA[<p>There is an occasion coming up and we would like to host some static content for the world to see on a web server. So we’ll create an EC2 instance and install Apache during the creation of the instance to do it. We’ll also create the index.html file to serve out our special content while we create the EC2 instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*h_w13Ke8RhPwRm8R" /><figcaption>Photo by <a href="https://unsplash.com/@hishahadat?utm_source=medium&amp;utm_medium=referral">Shahadat Rahman</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Requirements:</p><p>AWS account access and stable internet connection</p><p>Log in to the AWS Management Console and we’ll start by creating the EC2 instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/401/1*BMIWIeZF_hbF0KUyaPR6CQ.png" /><figcaption>AWS Management Console Home</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/198/1*O14c-Q3kWLb5CUVCJMakbQ.png" /><figcaption>Launch Instance drop-down</figcaption></figure><p>Name your instance, select an AMI (Amazon Linux 2 AMI), select the type ( t2 micro) select Key pair, and use the default VPC with security group. Click <strong>Allow SSH from custom</strong> (your IP address), click <strong>Allow HTTP traffic</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/1*0fmuQ4PZrdMV3FfdoFZsgA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/272/1*cLg1DTCp-OuqIWKMofxumA.png" /></figure><p>Leave the rest of the options as defaults and scroll down to the <strong>Advanced Details </strong>section:</p><p>At the <strong>User data </strong>section, copy in the below script:</p><p><em>#!/bin/bash</em></p><p><em>yum update -y</em></p><p><em>yum install httpd -y</em></p><p><em>systemctl start httpd</em></p><p><em>systemctl enable httpd</em></p><p><em>cd /var/www/html</em></p><p><em>echo “This is JAB’s test page running on Apache on an EC2 instance in the AWS Cloud” &gt; index.html</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/291/1*qgkGjqrRfxBjg2mbq9FyBg.png" /><figcaption>User data (script)</figcaption></figure><p>Click <strong>Launch Instance</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/339/1*aLFypD76AO0n4_FzyJ7OqA.png" /></figure><p>Click <strong>View all Instances</strong> in the bottom right corner of the screen</p><p>Now let’s connect to our new instance to verify that our Apache web server is up and running. Click <strong>Connect to Instance </strong>and in this case, select<strong> SSH Client.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/322/1*GIHW1x3vu96P6eUq9SCZ4Q.png" /></figure><p>From your terminal, navigate to the directory where your Test Key is located. SSH into your instance as seen below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/321/1*O9MGmOECuLZSVm-SC19Vlg.png" /></figure><p>We have successfully securely connected to our EC2 instance using our Test Key. Now let’s peek into the html directory and verify the contents of the index.html file:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/329/1*BSDcWjyvx599VD4pPy_BfQ.png" /><figcaption>Output of cat index.html</figcaption></figure><p>Yes! That is what we expected the cat command to produce. Now let’s see if we can connect to our EC2 instance from any IP address to see if we get the output from above.</p><p>Return to the AWS Management Console, grab the Public IP of the EC2 instance and browse to that URL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/705/1*b7nEaXVhhDU7I2S1bKXJkQ.png" /></figure><p>Hope you enjoyed my short article. Thanks for stopping by!</p><p><em>*Don’t forget to terminate your instance*</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4b8a575d427" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using git and GitHub (forking and pull requests)]]></title>
            <link>https://medium.com/@janella.baker/using-git-and-github-forking-and-pull-requests-653bdb095437?source=rss-ba6f93f384af------2</link>
            <guid isPermaLink="false">https://medium.com/p/653bdb095437</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Janella Baker]]></dc:creator>
            <pubDate>Sun, 29 May 2022 11:37:40 GMT</pubDate>
            <atom:updated>2022-05-29T11:37:40.217Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*P1XFmHBDpr05d6a-" /><figcaption>Photo by <a href="https://unsplash.com/@synkevych?utm_source=medium&amp;utm_medium=referral">Roman Synkevych 🇺🇦</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Introduction</strong></p><p>Soooooo what is git?</p><p>And what is GitHub? Are they the same thing? Why would I even need to use git and/or GitHub?</p><p>Git is free and open source software that can run on your local machine and its main purpose is to help with source control. Meaning, git will help you track changes that you (or someone else that you allow) make to your files. It is an extremely powerful tool that developers can use to collaborate on large files with dozens of lines of code or thousands of lines of code.</p><p>GitHub is an online hosting service that can be used to store the files for your project so that multiple developers can work on it in a collaborative manner. GitHub has a free tier that will allow multiple developers to work together by pulling down files from a shared location, making changes locally, and then pushing up those new edited files back to the shared location for a potential merge.</p><p>In this article, I will use git on my local machine to “fork” a repository from GitHub so that I can make changes to a file. I will then send a pull request to the repo owner so that they can review my changes and accept or deny my request to merge my changes with the existing file. I will use a combination of the command line and other developer tools to accomplish this task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Etwk-jOJ9nrYIbQR" /><figcaption>Photo by <a href="https://unsplash.com/@thisisnando?utm_source=medium&amp;utm_medium=referral">Fernando Andrade</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>(Note: Fork is a term used by developers to copy/clone a repository so that you can make changes without affecting the main repository.)</p><p><strong>What we will need:</strong></p><ol><li>Computer with admin creds and/ or CentOS 8 Virtual Machine</li><li>Stable internet connection</li><li>git software and a GitHub account (free tier)</li><li>Visual Studio Code or Vim (editor)</li><li>Git Bash and GitHub Desktop (optional)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8j-DRGRD-hB3mJlN" /><figcaption>Photo by <a href="https://unsplash.com/@clemhlrdt?utm_source=medium&amp;utm_medium=referral">Clément Hélardot</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Step 1: </strong>Access git either through your terminal or through GitHub Desktop by first installing git. From your CentOS 8 virtual machine’s terminal, type:</p><blockquote>sudo yum install git</blockquote><p>Git will install and then we will need to configure git with the following settings:</p><blockquote>git config — global user.name &lt;”GitHub username”&gt;</blockquote><blockquote>git config — global user.email &lt;”email_address”&gt;</blockquote><blockquote>git config — system core.editor Visual Studio Code</blockquote><p>I am not using a CentOS server VM because I already had git installed on my local PC. The steps above are to be used if you would prefer to download git to a VM that you can terminate later.</p><p>Alternatively, you can download git for Windows PC’s from this URL: <a href="https://git-scm.com/download/win">https://git-scm.com/download/win</a></p><p>Either way, once you have git installed and configured, you can verify the configuration settings. Navigate to your home directory and use the<strong> ls -al</strong> command. In the below screenshot, I am using <em>Git Bash</em> for my terminal on my local PC.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z7Hb0kaXB8wOvKmUzQZMkA.png" /><figcaption>Settings verification</figcaption></figure><p><em>Note: Use ls -al to verify the hidden file “.gitconfig” is present. You can use vim on .gitconfig to view the file changes such as username, email address, and core editor.</em></p><p>So now that git is installed and configured, let’s fork a repository to our local system so that we can make changes without affecting the main files.</p><p><strong>Step 2:</strong> Open a web browser and navigate to a repository on GitHub that will allow you to fork a repository. In this case, I will navigate here: <a href="https://github.com/LevelUpInTech/LevelUpTeam">https://github.com/LevelUpInTech/LevelUpTeam</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kmfcWPAOhMvx6SV3sOS9Ng.png" /><figcaption>Repo URL</figcaption></figure><p>Click on the <strong>Fork</strong> button to fork this repo to your local system using https:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/623/1*AvXYre8BzPWnnNPNCWLA2w.png" /></figure><p>From here, you can click <strong>Open with GitHub Desktop</strong> and you will see a screen like below. Alternatively, you can open your terminal and use the <strong>git clone </strong>command along with the URL of the repo to add this repository to your local system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v4SLsXO1TApHP6mbK2A46Q.png" /><figcaption>GitHub Desktop</figcaption></figure><p><strong>Step 3:</strong> Make changes to a file that you need to edit. In this instance, I will use Visual Studio Code to edit the linux.sh script by making a few small changes. From above, click <strong>Open in Visual Studio Code. </strong>Alternatively, you could type <strong>vim linux.sh</strong> at the terminal to drop into the vim editor to edit the script.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*36IFLri06rGaBnWVzqZ_Yw.png" /><figcaption>Visual Studio Code</figcaption></figure><p><strong>Step 4:</strong> After editing the script, save your changes, exit out of the editor, and test the script before you make a pull request. It is good practice to ensure that whatever changes you made to a file are what you intended to make. Open your terminal and navigate to the location of the script. Execute the script by typing <strong>bash linux.sh </strong>at the command prompt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/951/1*CDB1P3QgZBIUdR3hKmrQnw.png" /><figcaption>Script execution</figcaption></figure><p><strong>Step 5:</strong> Let’s check the status of our file by typing <strong>git status</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/870/1*L2uE41sGTnLPwUplNZk0UQ.png" /><figcaption>Git Status</figcaption></figure><p>As we can see, we have modified the linux.sh script on our main branch and now we need to use the <strong>git add</strong> and <strong>git commit</strong> command to commit the changes. Use the <strong>-m</strong> option with the git commit command to add a message that describes the change(s) you made. Type the commands as shown below but use your own message in the “” after the -m option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*DAiNrmE21AVcI9Je-jHuRA.png" /><figcaption>Git add and git commit -m</figcaption></figure><p><strong>Step 6:</strong> Push the edited file to your local repo and then prepare to push to GitHub. I will use GitHub desktop to do this because I am already authenticated to GitHub. Add your message in the lower left corner and click <strong>Push origin</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uavdVHpbViS-xRPOtvE_-w.png" /><figcaption>Push origin</figcaption></figure><p>After you have pushed your file to your local repo, you can now use GitHub Desktop to open the repo page in GitHub via your web browser. From above, click <strong>View on GitHub.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8uFUGodRgTJ5fDkXYO6pug.png" /><figcaption>My commit is here</figcaption></figure><p>Notice from above, my branch (from when I forked the original repo) is denoted by <strong>jbak2030/LevelUpTeam</strong> and my branch is <strong>2 commits ahead</strong> of the master branch- <strong>LevelUpInTechmain</strong>. So I will now need to initiate a Pull Request so that my changes can be added to the master repo.</p><p><strong>Step7:</strong> From your branch, click <strong>Pull requests</strong> and you will see a screen similar to below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3zI4eoWqQ4iciSXTSPAsvg.png" /><figcaption>Pull Request</figcaption></figure><p>Click <strong>New pull request</strong> and view the changes to the file(s) that you have edited:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U4n_tTxmSQI1W94HAgmMhA.png" /><figcaption>File changes</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x42_HWgu51NtL3BUjZbJsQ.png" /><figcaption>Comment</figcaption></figure><p>Click <strong>Comment</strong>, add your comment(s), and finally click <strong>Create Pull Request</strong>.</p><p>The owner of this repository will get a notification of this pull request. After review, the owner will either accept or deny the pull request to merge your branch with the master repository. Fingers crossed!!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*shZvVT9rHwh-8ylS" /><figcaption>Photo by <a href="https://unsplash.com/@macroman?utm_source=medium&amp;utm_medium=referral">Immo Wegmann</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=653bdb095437" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Install NGINX Web Server on CentOS 8 Server]]></title>
            <link>https://medium.com/@janella.baker/how-to-install-nginx-web-server-on-centos-8-server-24adb756990b?source=rss-ba6f93f384af------2</link>
            <guid isPermaLink="false">https://medium.com/p/24adb756990b</guid>
            <category><![CDATA[nginx]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[cli]]></category>
            <category><![CDATA[centos-8]]></category>
            <category><![CDATA[web-server]]></category>
            <dc:creator><![CDATA[Janella Baker]]></dc:creator>
            <pubDate>Sun, 15 May 2022 17:02:30 GMT</pubDate>
            <atom:updated>2022-05-15T17:02:30.806Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HyCHTlXPQUv--_Zd" /><figcaption>Photo by <a href="https://unsplash.com/es/@markusspiske?utm_source=medium&amp;utm_medium=referral">Markus Spiske</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I had been revisiting some older material I already had and accessing some new material through <strong>A Cloud Guru </strong>to refamiliarize myself with actions needed to install a web server on a virtual machine (VM). You may be asking yourself why would anyone ever need to install a web server, virtual machine or not. hmmmm.</p><p>Well, there may come a time in your life when you need to serve web content out to the world. For example, you could serve web pages that store your content such as photos or videos, products that you want to sell, or causes that you want to raise money for. More specifically, your web server is designed to store, process, and deliver web pages to your user(s). NGINX can be used as a web server, a reverse proxy, and/or a load balancer.</p><p>For this installation, you will need to follow the below steps in order.</p><blockquote>Prerequisites:</blockquote><blockquote>1. CentOS 8 Virtual Machine access</blockquote><blockquote>2. A user account that can use elevated privileges (sudo)</blockquote><blockquote>3. An internet connection</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qu3Pkf4582Nq7oFp" /><figcaption>Photo by <a href="https://unsplash.com/@tma?utm_source=medium&amp;utm_medium=referral">Tianyi Ma</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I will be using a cloud server from the “<em>Cloud Playground</em>” in <strong>A Cloud Guru</strong> (formerly Linux Academy). But you can use any virtual environment such as Amazon Web Services (AWS), VMware Workstation/ Player, or Oracle VM VirtualBox.</p><p>From A Cloud Guru’s Cloud Playground:</p><p>Click on Cloud Servers</p><p>1. Click + New Server</p><p>2. Select CentOS 8 from the Distribution Dropdown</p><p>3. Select North America from the zone dropdown (if you’re in North America)</p><p>4. Select Small — 2 units from the Size dropdown</p><p>5. Click Create Server</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*yWNaPtzDdPdPyesJ2NMk4w.png" /><figcaption>Create New Server</figcaption></figure><p>Wait for new CentOS 8 Server to provision (get ready for use).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*yLwhMa6CtWkFuB1Qjoj-jg.png" /><figcaption>Server provisioning</figcaption></figure><p>The status of the server will change multiple times from creating, to starting, to assigning IP, etc. until the server is <strong>Ready </strong>for use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/795/1*RAPKdizTwUafFTufIAkcMw.png" /><figcaption>Server Ready</figcaption></figure><p>Open a Terminal from your host computer (Windows users can type cmd in the search box)</p><p>Type the following command:</p><p><strong>ssh </strong><a href="/service/mailto:cloud_user@34.217.128.37"><strong>cloud_user@34.217.128.37</strong></a></p><p>NOTE: The above IP address is my public IP address that was assigned to me by the Cloud Provider. It is valid for a few hours or until I delete my server. Your public IP address will be different than the one above.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*cgTSl7Km8nLINsXp26l6Dw.png" /><figcaption>Successful ssh into server from host machine</figcaption></figure><p>NOTE: You will have to change your password from the temporary password that was provided by the Cloud Provider to a new password.</p><p>Now that we have our server ready to go, let’s install NGINX so we can serve a webpage.</p><p>At the prompt, type the following commands:</p><p><strong>sudo yum update</strong></p><p><em>(this will update the presently installed packages to their latest version)</em></p><p><strong>sudo dnf install nginx</strong></p><p><em>(</em>dnf <em>is a software package manager that will help us install NGINX)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*rnJ_lUTKYwOXDcQ0Of9MPA.png" /><figcaption>Update server and install NGINX</figcaption></figure><p>As we can see above, we need to download 881 kb of packages and after installation, the nginx packages will be 2.0 Mb in size.</p><p>We will type <strong>y</strong> to answer the last question and install NGINX</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*9Jilk_Mx1Ud0Sp77YHFOpg.png" /><figcaption>NGINX install complete</figcaption></figure><p>Sweet! NGINX installed without issue. Now it’s time to configure the web server.</p><p>We need to <strong>enable</strong> and <strong>start</strong> the NGINX server</p><p>Type the following commands:</p><p><strong>sudo systemctl enable nginx</strong></p><p><em>(Enables the NGINX server)</em></p><p><strong>sudo systemctl start nginx</strong></p><p><em>(Starts the NGINX server)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*HRqpHWIcuX1d4uP9RpORmw.png" /><figcaption>Enable and start NGINX</figcaption></figure><p>Now we need to adjust the firewall rules so users can access our web server:</p><p>Type the following commands:</p><p><strong>sudo firewall-cmd — permanent — add-service=http</strong></p><p><em>(adds the port 80 http service to the FW services of NGINX)</em></p><p><strong>sudo firewall-cmd — permanent — list-all</strong></p><p><em>(lists the services that are currently enabled)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/909/1*4UmT-VNRi-yaQtsb01G-9A.png" /><figcaption>Add http to services</figcaption></figure><p>Note that http (web server port) is listed in the services section of the NGINX server</p><p>Now, let’s restart the firewall and navigate to our public IP URL</p><p>Type the following command:</p><p><strong>sudo firewall-cmd — reload</strong></p><p><em>(restarts the FW)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/653/1*Ux0b9wo5_y5fv8glGm1UGQ.png" /><figcaption>Restart the firewall</figcaption></figure><p>Open a web browser, and browse to the Public IP address that we were assigned from the Cloud Provider.</p><p>In this case, browse to <a href="http://34.217.128.37/">http://34.217.128.37</a></p><p>If everything went well, you will have the below screenshot displayed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*mtxGXN0nxqyVypLKdpQWUw.png" /><figcaption>Success!</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pLNcHUXTXQoP2rjk" /><figcaption>Photo by <a href="https://unsplash.com/@javaistan?utm_source=medium&amp;utm_medium=referral">Afif Kusuma</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24adb756990b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>