When we talked about the choice of home data center software environment, we mentioned LNMP (LAMP). Although we mainly use Docker to deploy home data center applications later, LNMP (LAMP) is still the choice of many production environments.

Manually building a LNMP (LAMP) environment is actually quite complicated, because it involves installing many related components and a lot of compiling operations, which is quite troublesome for novices. However, there is now a simple solution, which is to build the environment through the software store of the Linux panel. Take the Baota Linux panel as an example:

You can also install common tools such as redis and phpmyadmin.

Therefore, with the help of the Linux panel, you can easily build a LNMP (LAMP) environment and install common tools (such as redis). Just click the mouse and select the installation on the right side of the page.

I have used two kinds of Linux panels: Baota Linux Panel and 1panel. The interface of 1panel is cleaner and neater, and it is not as commercial as Baota Panel (after all, it is a free version, which is normal). However, there is a problem with 1panel, that is, the software installed in the software market is all installed in docker, which is a bit awkward, because if I really want to install it in docker, I have many choices (such as using Portainer), why must I install a panel and use docker? The purpose of installing Linux panel may be to make source code installation more convenient? So I didn't use 1panel panel later.

Another advantage of the Baota Linux Panel is that the Fortress Cloud Control Platform can manage multiple Baota Linux Panels at the same time:

However, this method may need to be combined with virtual networking technology, because a fixed IP must be assigned to each Baota Linux panel as the management IP of the Bastion Operation and Control Platform. If it is only accessed within the intranet, it is fine, but once you need to manage the panel on the cloud host, it will be troublesome. For example, if the Baota Linux panel is installed on the cloud host and the Bastion Operation and Control Platform is installed on the home intranet, the panel on the cloud host cannot specify a fixed public IP for the Bastion Operation and Control Platform from the home broadband public IP. At this time, a fixed IP of virtual networking is needed.

The following is the interface of the Pagoda panel. The red frame on the left is the menu bar that supports its functions:

If you are deploying source code and building a LNMP (LAMP) environment on the Baota panel, the menus on the left, such as website, FTP, database, and file, are very practical. If you are building a docker, you can also perform simple management directly under the Docker menu on the left:

Therefore, the pagoda panel is actually sufficient to meet the needs of most people.

But for me, I just use the reverse proxy function of the Baota panel website menu. In fact, if it is just a reverse proxy function, you don’t have to use the Baota panel, you can also use NPM (Nginx Proxy Manager), but I can also run some scheduled scripts with the Baota panel, which has more functions, so I don’t use NPM. You can choose the way to build a reverse proxy that suits you.

This chapter will briefly introduce the Baota Linux panel. After all, the reverse proxy running on it is the main entrance to my home data center. As for other functions, such as the source code construction of LNMP and other environments, if you need it in the future, you can try it yourself, so I won’t say more.