If you don't ask for a thorough understanding of everything, you will be blind when something happens - Apache server configuration memo for PHP development

Follow this configuration process and your journey will definitely be smooth and safe.

I made a small PHP program yesterday and wanted to run it locally to test it, but my work computer didn’t have an installation environment, so I downloaded a wamp and everything went smoothly, including Apache, Mysql, and PHP. Start the wamp service, enter "http://localhost" in the browser, the access is normal, and the wamp homepage pops up. Therefore, I want to configure my own CrashServer website into Apache and test it by accessing it locally through a virtual domain name. As a result, I encountered many problems. After doing some research on Google today, I finally found out that both Ren and Du are connected.

1. First of all, Apache’s configuration files are httpd.conf and httpd-vhosts.conf. Let’s first look at the default configuration of httpd.conf after wamp is installed.

<span>DocumentRoot "d:/wamp/www/"

</span><span><</span><span>Directory </span><span>/></span><span>    AllowOverride none
    Require all denied
</span><span></</span><span>Directory</span><span>></span><span><</span><span>Directory </span><span>"d:/wamp/www/"</span><span>></span><span>    Options Indexes FollowSymLinks
    AllowOverride all
    Require local
</span><span></</span><span>Directory</span><span>><br></span>

# Virtual hosts
#Include conf/extra/httpd-vhosts.conf

<span> </span>

If you want to access the website through a virtual domain name, you need to configure httpd-vhosts.conf. Then you need to start httpd-vhosts.conf, because it is closed by default, so remove the # in front of #Include conf/extra/httpd-vhosts.conf in the configuration file. So httpd-vhosts.conf is enabled, then we edit the httpd-vhosts.conf file.

2. The location of the httpd-vhosts.conf file is in conf/extra in the apache directory. The Include conf/extra/httpd-vhosts.conf above actually tells you its location.

In this file, add the configuration of my CrashServer website above:

<span>NameVirtualHost *:80</span><span><</span><span>VirtualHost </span><span>*:80</span><span>></span><span>    DocumentRoot "D:/wamp/www/CrashServer"
    ServerName crash.com
</span><span></</span><span>VirtualHost</span><span>></span>

First of all, my CrashServer is placed under wamp/www, which is the default website directory of wamp. Secondly, I want to test it locally At that time, you can access CrashServer using crash.com, so the configuration is as above.

Here, in order for us to access the local site through crash.com, we need to modify the hosts file and add 127.0.0.1 crash.com.

At this point, the configuration is completed, so I restarted Apache, entered crash.com to access, and the result was normal access. However, when accessing with localhost, the homepage of wamp originally appeared, but now CrashServer is displayed, so we need to add 127.0.0.1 localhost to hosts, and add the localhost site configuration to httpd-vhosts.conf. Now This is what it looks like:

<span>NameVirtualHost *:80

</span><span><</span><span>VirtualHost </span><span>*:80</span><span>></span><span>    DocumentRoot "D:/wamp/www"
    ServerName localhost
</span><span></</span><span>VirtualHost</span><span>></span><span><</span><span>VirtualHost </span><span>*:80</span><span>></span><span>    DocumentRoot "D:/wamp/www/CrashServer"
    ServerName crash.com
</span><span></</span><span>VirtualHost</span><span>></span>

OK, this is basically the end. The website is configured and it looks very, very simple. But this is not the case for me. I encountered the following problem yesterday.

First of all, my CrashServer was not placed under wamp/www at the beginning, but under E:360Downloads, so I had the following configuration:

<span><</span><span>VirtualHost </span><span>*:80</span><span>></span><span>    DocumentRoot "E:/360Downloads/CrashServer"
    ServerName crash.com
</span><span></</span><span>VirtualHost</span><span>></span>

That’s right, the paths are correct, virtual The domain name is correct, but when accessing it, it prompts 403 Forbidden, no permission. So Google, oh, realized that it was necessary to add permissions to the CrashServer directory, so it modified the configuration as follows:

<span><</span><span>VirtualHost </span><span>*:80</span><span>></span><span>    DocumentRoot "E:/360Downloads/CrashServer"
    ServerName crash.com

    </span><span><</span><span>Directory </span><span>E:/360Downloads/CrashServer</span><span>></span><span>        Order Allow,Deny
        Allow from All
        Require all granted
    </span><span></</span><span>Directory</span><span>></span><span></</span><span>VirtualHost</span><span>></span>

Restart Apache, and access is normal. First of all, the new Directory can be added in httpd.conf or httpd-vhosts.conf. I think it is better to add it in the latter. The configuration content is clearer and the project directory permissions follow the project. Site configuration. In the newly added Directory above, we have added permissions to the CrashServer directory under 360Downloads and allowed access, so we no longer prompt 403 Forbidden.

This problem is so simple and easy to write now, but when the problem occurs, it is very disturbing and depressing. For projects outside wamp/www, you need to give the project directory permissions. Note:

<span>Order Allow,Deny
Allow from All
Require all granted</span>

These three items are indispensable. This is configured to allow external computers to access the server site.

3. After solving the problem today, I thought of accessing my site through other devices under the same LAN, so I used my mobile phone to enter my computer’s IP in the browser, but it couldn’t be accessed. I Googled it again, and it turned out that I needed to modify httpd.conf. The configuration in:

<span><</span><span>Directory </span><span>"d:/wamp/www/"</span><span>></span><span>    Options Indexes FollowSymLinks
    AllowOverride all
    Require local
</span><span></</span><span>Directory</span><span>></span>

Among them, Require local is not listed by Google, but judging from the name, it only allows local access, so it is changed to Require all granted, allowing all requested access, and the mobile phone can access it.

Reference, http://roteg.iteye.com/blog/1465380, here is an explanation of access verification configuration.

Here, there is a configuration blog post written by a foreigner, which is very good, https://www.kristengrote.com/blog/articles/how-to-set-up-virtual-hosts-using-wamp#wamp-step-7 , but the only thing is that in his Step 7, he added permissions to the project directory:

<span><</span><span>Directory </span><span>C:/Users/Kristen/Documents/Projects</span><span>></span><span>    Order Deny,Allow   
    Allow from all 
</span><span></</span><span>Directory</span><span>></span>

but the Require all granted was missing, which resulted in 403 Forbidden in the end, which made me very depressed.

This configuration is performed in the following wamp environment:

At this point, the PHP site is configured under Apache, and everything is completed.

The above has introduced the memorandum on configuration of the Apache server for PHP development if you don’t seek a thorough understanding of everything, and you will definitely be blind when encountering problems. It includes the relevant content. I hope it will be helpful to friends who are interested in PHP tutorials.