Issues encountered in the project build deployment:
1. Do not use hash, how to solve the problem of refreshing page 404?
Description
root specifies the project address path, which defaults to the HTML under Nginx
Index default Access Index file
Try_files here is actually changed by if, meaning that if the URI exists, then access the URI resource, if the URI does not exist, then access to the directory of the index.html file, thereby resolving the Refresh page 404 error.
2. Two-layer file path Refresh with resource load error issues
Premise: When building the project, use NG build--base-href./success, but when deploying the server side (using Nginx), the following problems occur:
Visible, redundant records layer path, so there is a problem with the path, change the following:
Build with NG build--base-href/Package project, or direct NG build because the default is/path, you can view the index.html file:
Deploy, find problem solving, done!
NG Build--base-href Setup problem