Detailed explanation of Apache website service configuration based on Linux

As an open source software, Apache is one of the most widely used web applications. Apache has two main versions, 1.X and 2.X. Generally, we use version 2.X, which supports many new features compared to version 1.X. The address for downloading the Apache source code package is: https://httpd.apache.org. After downloading the source code package, start preparing for installation:

1. To avoid port conflicts, program conflicts and other problems, if there is an httpd service installed in rpm mode, it is recommended to uninstall it.

2. Mount the system image, switch to the Packages directory in the system disk, and install related dependency packages (note that it is best to install them one by one, because if some installation packages have been installed, installing the following installation packages at once will result in an error)

3. Unpack the httpd source code package, specify the release directory, and then switch to the expanded source code directory:

4. Configuration:

In the above configuration command, the meaning of each option is as follows:

--prefix: Specifies the directory where the httpd service will be installed.

--enable-so: Enable dynamic module loading support, so that httpd has the ability to further expand its functions.

--enable-rewrite: Enable the web address rewriting function for website optimization and directory migration maintenance.

--enable-charset-lite: Enable character set support to support web pages encoded with various character sets.

--enable-cgi: Enable CGI script support to expand the application access capabilities of the website.

5. Execute the make && make install command to compile and install:

If an error occurs during the above configuration, compilation, and installation process, and command errors are excluded, it is usually because a dependency package is missing. Check whether any dependency package is missing!

6. After the installation is complete, switch to the directory where the installation is successful, and you will see the following directories:

The purpose of each major subdirectory is as follows:

• bin: stores various executable program files of httpd service. Including the main program httpd, service control tool apachectl, etc.
• cgi-bin: stores various CGI program files.
• logs: stores the log files of httpd service.
• conf: stores various configuration files of httpd service, including the main configuration file httpd.conf and the enhanced configuration subdirectory extra.
• htdocs: stores web documents, including the default homepage file index.html, etc.
• module: stores various module files of httpd service.

7. Optimize the execution path (depending on the actual situation, optimization is optional):

The httpd service installed through source code is a third-party service, so the program path is not in the default search path. If you want to start Apache now, you need to execute the command: /usr/local/httpd/bin/apachectl start, which is the absolute path of the program control file in the bin directory after the installation is complete, plus the required operation.

Then, in order to make this service more convenient to use, you can optimize the execution path. The process is as follows:

Add symbolic links for related programs:

In this way, when executing related commands, you don't need to enter a long path. If you want to start the service, just execute /usr/local/bin/apachectl start. However, this is still not as convenient as controlling the system service. Then, you can continue to add the httpd system service. There are two methods:

Method 1

Copy the apachectl file to /etc/init.d/httpd, and then edit the file:

Make the following changes, then save and exit:

Add system services:

At this point, you can use systemctl start/status/restart httpd to control the Apache service just like controlling the system service.

There is another way to add it as a system service, but you also need to edit the configuration file, which is more troublesome. It may be possible to further define the service. Personally, I think it is enough to understand it. If there are no special requirements, you can use the above method.

Method 2:

Create the httpd.service configuration file (pay attention to the path of the configuration file. The apachectl path written in the configuration file needs to be determined according to the actual situation)

The functions of each configuration item in the configuration file are as follows:

Both methods have their own advantages. Method 2 can define the service in detail, and you can also use systemctl enable httpd.service to set the httpd service to start automatically at boot, which is not possible with method 1.

Once the control of the service is optimized, you can perform basic configuration of the httpd service:

1. Edit the main configuration file httpd.conf of the httpd service

Execute /ServerName in the last line mode and add a line nearby: ServiceName www.aaa.com, which is used to set the domain name corresponding to the website. as follows:

Enter the last line mode to find ServerName:

After modifying the configuration content of the httpd.conf file, you can use the command apachectl -t or httpd -t to perform a syntax check on the configuration content. If there are no errors, it will be displayed as follows:

2. Deploy web documents:

For the newly compiled and installed httpd service, the website root directory is located in /usr/local/httpd/htdocs . You need to copy or upload the web site's web documents to this directory.

3. Check the access status of the web site

The httpd server uses two types of logs: access logs and error logs. The file names of these two logs are acces_log and error_log, both in the /usr/local/httpd/logs directory. You can use the command tail -f /usr/local/httpd/logs/access_log to dynamically view website access status.

4. The most important httpd.conf main configuration file

Comment lines in httpd.conf start with "#", and the rest are configuration lines. Depending on the scope of the configuration, the setting line can be divided into global configuration and regional configuration. Each global configuration is an independent configuration and does not need to be included in other task areas. Some commonly used global configuration items are as follows:

Except for the global configuration items, most of the configuration in the httpd.conf file is included in the zone. The regional configuration uses a pair of combined tags to limit the scope of the configuration item, as follows:

The above is the full content of this article. I hope it will be helpful for everyone’s study. I also hope that everyone will support 123WORDPRESS.COM.