[Deployment project] Record some pits stepped on

Record some pits stepped on

This post is used to record the pits and corresponding solutions that I encountered when deploying projects under windows and linux

Set up a second-level domain name

When you only have one domain name and don’t want to buy a new domain name (the domain name is actually very cheap, it’s expensive to rent a server), the second-level domain name is a very good choice. It directly adds a little setting on the basis of the first-level domain name The operation that can be completed
Add a record on the domain name application platform, as shown in the figure

below, there is no problem here. I directly add a new second-level domain name to the domain name I applied for, and then configure it on my overseas server (why? I won’t go into details if it’s overseas), it can be directly successful

Precautions

1. Linux system
   My server is installed with pagoda on linux and uses apache. If your server is also like this, you need to pay attention. Pagoda redefines the file path of the virtual host configuration in apache. Generally, we are directly in apache / The configuration is modified in the host_vhost.conf file in conf/extra . But if you are using the website in the pagoda, and then create a new site, he will configure a one-to-one configuration file with your new site under the path
   www/server/panel/apache/vhost
   (the file name is the same as your new site If you want to modify the root directory of this site or the corresponding domain name, you need to modify it here, otherwise it will not take effect if you modify it in the default vhost file of apache
2. The conflict between the deployed software
   The company's server is windows, and there are many projects running in the server before I deploy the project, but they use IIS, not Apache, I have not touched IIS at the beginning, So I built an apache environment by myself, and then put the project in it for deployment. At that time, I didn't know domain name management and dns analysis (of course, I'm not very familiar with it now, it's too far away). When I first deployed, I directly accessed the project and API directly through the form of ip plus port number. Called, now because I understand some knowledge of the second-level domain name, I now decide to use the second-level domain name to access and call the original project. When I successfully access the project through the second-level domain name on the Linux server, I am confident in the company The same operation is also carried out on the Windows system, but no matter how the configuration is, the project cannot be accessed directly through the second-level domain name, but if it is in the form of the second-level domain name + port number, it is possible, which makes me baffled Solution, I realized later that it may be caused by a conflict between the existing iis on the company's server and my apache. The
   solution: see whether you deploy more projects with iis or apache. I am here with iis There are many projects deployed, so I mainly use iis here, and add all the projects originally configured on apache into iis, and then solve the problem that the project cannot be accessed directly through the second-level domain name.
   If you are mainly based on apache, then you need to modify the forwarding and other things in the httpd.conf configuration file in apache, because the time is limited, I will not continue to study~ (deployment and operation are too tortured...wrong , is the development is too tortured 555)
   You can see this post

https://www.bbsmax.com/A/mo5kxVB4dw/

One more word, I personally feel that iis is more comfortable to use than apache, maybe because it has its own visual interface, apache does not have it

file access permissions

After deploying the project with iis, it was found that the content related to admin data management could not be opened, and the error was reported as shown in the figure below

Solution: Find the corresponding path on the server, then right-click the corresponding folder, enter properties, click Security, edit the permissions of the current system user, and tick Write, as shown in the figure below, there are other problems related to

deployment It's all updated here