Skip to main content

LEMP stack (minus the PHP)

Today we’re going to be talking about building a LEMP stack! Many of you may be familiar with LAMP stacks (Linux Apache MySQL PHP). A LEMP stack is Linux, Nginx, MySQL and PHP (however we’re substituting PHP with Python because.. well…. Php.

I’m currently using a KVM server with a Linux Mint jumpbox. I SSH in with the -X switch to bring up the virt-manager GUI. However, you do not need this. This config can work whether you’re running a Linux VM on Hyper-V, ESXi, KVM, OpenStack, AWS, Azure, etc. You can even do this on a local Linux install.

The first thing we’re going to do is pick a Linux distro. As I love me some RedHat, we’re going to go with the free developer license for RedHat. You can sign up for this on RedHat’s subscription site and have up to 16 VM’s licensed and subscribed for free. If you do not want to do this, feel free to download CentOS.

The first thing we will install is the epel-release repo. This is due to yum missing some packages. The two ways to do this are;

```sudo rpm -ivh```
```yum update```

Next, we are going to install Nginx

```yum install nginx -y``` (the -y is so you don’t get prompted to choose yes)

To start Nginx  and confirm it’s up, run;

```systemctl start nginx```
```systemctl status nginx```
```curl privateipaddress```

Once that is up, you should be able to go into a web browser, type in your private IP address over port 80, and see the Nginx splashpage.


Up next, we will install MySQL. This varies based on what application you will be working with and the requirements. In our case, we will go with the latest and greatest.

```rpm -ivh mysql80-community-release-el7-1.noarch.rpm```
```yum update```
```yum install mysql-server```

To change the MySQL default password, take a look at /var/log/mysqld.log. You will get the default MySQL password. To log into mysql, type:

```mysql –u root –p temppassword```

After you confirmed you can log in, run through;

After that, confirm you can log into MySQL with your new password.

Finally, we will install the P in LEMP. It’s typically PHP, but today we will use Python!

We will install development tools so we can compile our install of Python3.6. Do the exact following;
```sudo yum groupinstall -y "Development Tools"```

Cd /tmp (this is where your installs should go before running. /tmp removes automatically every 10 days so you don’t have files sitting around that you don’t need).


```tar –xvf Python-3.6.3.tar.xz```
```ls Python-3.6.3```
```make install```

After this, type “which python3”.

Congrats! You have officially compiled your first (maybe your first) application AND built your first LEMP stack. Now go and tell everyone of your god-like status.


Popular posts from this blog

So, you want to be a Cloud Engineer?

In 2019 one of the biggest pieces of tech is the cloud. Whether it be public cloud or private cloud, cloud technologies are here to stay (for now). I predict that Cloud Engineering will be a very big part of IT (and development) for another 5-10 years. Today I want to share with you my journey in becoming a Cloud Engineer and some helpful tips. A career timeline to be a Cloud Engineer can go like so;

Desktop Support > Junior Sysadmin > Sysadmin > Sysadmin/Technical Lead > Engineer >  Cloud Engineer.

Although our career paths may not align, I believe that this progression is very import. Let me tell you why.

Helpdesk/Desktop Support Helpdesk and desktop support get your feet wet. It allows you to understand technology and how it's used in the workplace from a business perspective. It shows you what technologies may be best in the current environment your in and how to support those technologies. It also teaches you soft skills and how to support people from a technic…

Monitoring your containers in an AKS cluster with Prometheus

Monitoring and alerting is arguably one of the most important thing in Cloud Engineering and DevOps. It's the difference between your clients stack being up and a client being down. Most of us have SLA's to abide by (for good reason). Today we're going to learn how to spin up Prometheus in an AKS cluster to monitor our applications.

1. Intermediate knowledge of Kubernetes
2. An AKS cluster spun up in Azure

Recently AKS supports Prometheus via Helm, so we'll use that for an automated solution to spin this up. This installs kube-prometheus, which is a containerized version of the application. With raw Prometheus, there are a few things that are needed for the operator;

1. Prometheus: Defines a desired deployment.
2. ServiceMonitor: Specifies how groups of services should be monitored
3. Alertmanager: Defines the operator to ensure services and deployments are running by matching the resource

With kube-prometheus, it is all packaged for you. This means configuri…

Spinning up a Kubernetes cluster with Kubeadm

In today's world, we have several public cloud technologies that will ultimately help us with spinning up these infrastructures. This however comes with a price. Because a public cloud provider (like AWS or Azure) handles the API/master server and networking, you'll get something up quick, but miss some key lessons of spinning up a Kubernetes cluster. Today, I'll help you with that.

There are some pre-reqs for this blog:
1. At least 3 VM's. In my case, I'm using my ESXi 6.7 server at home.
2. Basic knowledge/understanding of what Kubernetes is utilized for.
3. Windows, Mac, or Linux desktop. For this blog, I am using Windows 10.

The first thing you want to do is spin up three virtual machines running Ubuntu18.04. You can use a RHEL based system, but the commands I show and run (including the repos I'm using) will be different.

I have already set up my 3 virtual machines. I gave them static IP addresses as I have found API/configuration issues if the VM shuts do…