Shulou(Shulou.com)06/02 Report--

As the project development draws to a close, we begin to deploy the project in a production environment, and the development phase does not use nginx. The project adopts SOA architecture and multi-system development, including service system, middle platform system, background system, financial system, interface system, dispatching system, report system and so on. This kind of distributed system generally uses nginx to do load balancing.

As soon as the company was founded, I came in to be an architect, responsible for all the research and development of the company, and set up the entire technical architecture of the company. at first, all the core business codes were basically coded by themselves. The system has developed from only one pc terminal to three app in pc, backstage and Android, and three app in iOS. More and more products have been done, and they are personally responsible for recruitment interview and training. There have been helplessness and distress in many cases before, because they are responsible for the entire structure of the company, but also responsible for the coding of the core business, the overcoming of technical difficulties, and the recruitment and training of new employees. Now the team has grown to 16 people, and these are all R & D personnel.

Looking back on this journey, I feel that the mountain that seemed impossible to climb before is no more than this. Maybe this is growth. Growth is always accompanied by a little sweat and tears. Since I am responsible for everything in the team, I have to take responsibility for database maintenance, data migration, indexing and other performance optimization, project deployment, and so on. Don't ask me why the company doesn't have DBA. Why is there no operation and maintenance? I really can only give you a look, let you slowly to experience.

Don't say much, just start the sharing of technical practical information.

The advantages of nginx as a load balancer there are many introductions on the Internet, and I won't introduce them any more here. Because there are many systems to deploy, involving domain names, second-level domain names, multiple domain names and so on. In the actual deployment, we have encountered many pitfalls due to lack of familiarity with nginx, in which the configuration of multiple domain names, xxxx.com forwarding to www.xxxx.com, access domain name forwarding to tomcat projects, and so on, now summarize a solution to the crater.

If you point the domain name xxxx.com to the tomcat project in port 8082, you will talk about an episode before making this introduction. For example, you need to switch to www.xxxx.com to access xxxx.com, which many people will ignore.

Now, if you want to deploy the central server, backend and financial system, find nginx/conf/nginx.conf and modify the configuration:

Upstream web {server localhost:8082;} upstream admin {server localhost:8083;} upstream finance {server localhost:8084;} server {listen 80; server_name finance.xxxx.com; # charset koi8-r; # access_log logs/host.access.log main; location / {proxy_pass http://finance; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr Proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;} # error_page 404 / 404.html; # redirect server error pages to the static page / 50x.html # error_page 500502 503 504 / 50x.html; location = / 50x.html {root html;} server {listen 80; server_name www.xxx.com; # charset koi8-r; # access_log logs/host.access.log main Location / {proxy_pass http://web; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;} # error_page 404 / 404.html; # redirect server error pages to the static page / 50x.html # error_page 500502 503 504 / 50x.html; location = / 50x.html {root html } # proxy the PHP scripts to Apache listening on 127.0.0.1 php$ 80 # # location ~. Php$ {# proxy_pass fastcgi_param SCRIPT_FILENAME #} # pass the PHP scripts to FastCGI server listening on 127.0.0.1 proxy_pass 9000 # location ~. Php$ {# root html; # fastcgi_pass 127.0.1 fastcgi_param SCRIPT_FILENAME / scripts$fastcgi_script_name # include fastcgi_params; #} # deny access to .htaccess files, if Apache's document root # concurs with nginx's one # # location ~ /\ .ht {# deny all; #} server {server_name xxxx.com; rewrite ^ (. *) http://www.xxxx.com$1 permanent;} server {listen 80; server_name admin.xxxx.com; # charset koi8-r; # access_log logs/host.access.log main Location / {proxy_pass http://admin; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;} # error_page 404 / 404.html; # redirect server error pages to the static page / 50x.html # error_page 500502 503 504 / 50x.html; location = / 50x.html {root html } # proxy the PHP scripts to Apache listening on 127.0.0.1 php$ 80 # # location ~. Php$ {# proxy_pass fastcgi_param SCRIPT_FILENAME #} # pass the PHP scripts to FastCGI server listening on 127.0.0.1 proxy_pass 9000 # location ~. Php$ {# root html; # fastcgi_pass 127.0.1 fastcgi_param SCRIPT_FILENAME / scripts$fastcgi_script_name # include fastcgi_params; #} # deny access to .htaccess files, if Apache's document root # concurs with nginx's one # # location ~ /\ .ht {# deny all; #}}

The above configuration also includes the configuration for accessing xxxx.com to www.xxxx.com, as follows:

Server {server_name xxxx.com; rewrite ^ (. *) http://www.xxxx.com$1 permanent;}

The basic configuration of nginx is roughly like this. If you bind multiple domain names (whether first-level domain name or second-level domain name) and need to configure multiple server, you will find that these server configurations are similar, mainly by changing the server_name and proxy_pass direction. The upstream node is actually the access path to the proxy service.

If you visit the domain name at this time, you will find that the configuration of nginx is in effect, but the default interface of tomcat is currently displayed. This is basically the configuration of nginx, and then make some configuration changes to tomcat. Find the conf/server.xml in tomcat, comment out the default Host configuration, and add the following Host configuration:

The above is the configuration under the windows server. For linux, you only need to change the appBase and docBase to point to the project. The configuration of tomcat has also been completed. Restart tomcat and the access domain points to the project in tomcat.

Summary

The above is the nginx+tomcat single domain name and multiple domain name configuration introduced by the editor. I hope it will be helpful to you. If you have any questions, please leave me a message and the editor will reply you in time. Thank you very much for your support to the website!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.