Home > Article > Backend Development > PHP development Apache server configuration
PHP development Apache server configuration
- WBOYOriginal
- 2016-07-25 08:44:421269browse
|
Follow this configuration process and your journey will definitely be smooth and safe. I made a PHP applet 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 a lot of problems. After researching on Google today, I finally found 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.
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 for my CrashServer website above:
First of all, my CrashServer is placed under wamp/www, which is the default website directory of wamp. Secondly, I want to use crash.com to access the CrashServer when testing locally, 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 site configuration of localhost to httpd-vhosts.conf. Now This is what it looks like:
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 first, but under E:360Downloads, so I had the following configuration:
This is correct, the path is correct and the virtual domain name is also correct. However, when accessing, 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:
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 permission to the project directory. Note:
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 it needed to be modified in httpd.conf. Configuration:
Among them, Require local has not been published by Google, but as you can see from the name, it only allows local access, so it was 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 very good configuration blog post written by a foreigner, 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, add permissions to the project directory:
However, Require all granted was missing, which resulted in 403 Forbidden in the end, which made me very depressed. ------------------------------------------------- --------------------------------Supplementary 2015-07-13--------------------- -------------------------------------------------- ---------------------------------- Thanks to the only commenter in the comment for the reminder: Require all granted is only required on 2.4 and not required on 2.2. This makes it understandable why some of the technical articles published by Google mention require all granted, while others do not. ------------------------------------------------- --------------------------------end Supplementary 2015-07-13---------- -------------------------------------------------- ---------------------------------- This configuration is performed in the following wamp environment:
At this point, configuring the PHP site under Apache is complete. The above is the entire content of this article, I hope you all like it. |
