Consul与Nginx配置咨询：非Docker环境下如何起步？

Hey there! Since you’ve already got Spring + Consul up and running, let’s walk through exactly how to set up Nginx as your reverse proxy and load balancer—no Docker required. I’ll break this into clear, actionable steps:

Since your Spring apps are already registering with Consul, the main thing here is making sure Nginx can reach Consul’s HTTP API to pull service data:

• If you’re running Consul in dev mode, restart it with the client bound to all interfaces so Nginx can connect:

  consul agent -dev -bind=0.0.0.0 -client=0.0.0.0
  

  The -client=0.0.0.0 flag lets machines other than localhost (like your Nginx server) access Consul’s API and UI.
• Verify your services are registered properly: Visit Consul’s UI (default: http://<consul-ip>:8500) or run this curl command from your Nginx machine:

  curl http://<consul-ip>:8500/v1/catalog/service/<your-spring-service-name>
  

  You should see a list of your Spring service instances with their IPs and ports—this confirms Consul is ready to talk to Nginx.

Nginx doesn’t natively integrate with Consul service discovery, so we’ve got two solid paths: dynamic (production-ready) or static (for quick testing).

Option A: Consul Template (Dynamic, Production-Grade) #

Consul Template is a tool from HashiCorp that listens for changes in Consul (like services starting/stopping) and automatically updates your Nginx config, then reloads Nginx. Here’s how to set it up:

1. Install Consul Template: Download the binary matching your operating system (from HashiCorp's official distribution channels) and place it in your system’s PATH (e.g., /usr/local/bin/ on Linux).
2. Create an Nginx Template File (save as nginx-service-template.ctmpl):

   upstream spring_service_cluster {
     # This loops through all healthy instances of your service in Consul
     {{ range service "<your-spring-service-name>" }}
     server {{ .Address }}:{{ .Port }};
     {{ end }}
   }
   
   server {
     listen 80;
     server_name your-domain.com localhost;
   
     location / {
       proxy_pass http://spring_service_cluster;
       # Pass important headers to your Spring app
       proxy_set_header Host $host;
       proxy_set_header X-Real-IP $remote_addr;
       proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
     }
   }
   

3. Create a Consul Template Config File (save as consul-template-config.hcl):

   template {
     source      = "nginx-service-template.ctmpl"
     destination = "/etc/nginx/conf.d/spring_service.conf" # Where Nginx reads configs
     command     = "nginx -s reload" # Reload Nginx after updating config
   }
   
   consul {
     address = "<consul-ip>:8500" # Point to your Consul server/client
   }
   

4. Start Consul Template:

   consul-template -config consul-template-config.hcl
   

   Now, whenever a Spring service instance starts or stops, Consul Template will update your Nginx config and reload it automatically—no manual changes needed.

Option B: Manual Static Config (For Testing Only) #

If you just want to test the setup quickly without extra tools, you can hardcode your service instances into Nginx:

1. Open your Nginx config directory (usually /etc/nginx/conf.d/) and create a file like spring_service.conf:

   upstream spring_service_cluster {
     server 192.168.1.10:8080; # Your first Spring instance IP:port
     server 192.168.1.11:8080; # Your second Spring instance IP:port
     # Add more instances as needed
   }
   
   server {
     listen 80;
     server_name localhost;
   
     location / {
       proxy_pass http://spring_service_cluster;
       proxy_set_header Host $host;
       proxy_set_header X-Real-IP $remote_addr;
     }
   }
   

2. Reload Nginx to apply changes:

   sudo nginx -s reload
   

   Note: This is only for testing—if instances change, you’ll have to manually update the config and reload Nginx every time.

• Visit http://<nginx-ip> in your browser or use curl: You should see your Spring app’s response.
• Test load balancing: Stop one Spring instance—with Option A, Nginx will stop sending traffic to it automatically; with Option B, you’ll need to remove the instance from the config.
• Check Consul’s UI to confirm all healthy instances are being picked up by Nginx.

Quick Tips #

• Make sure firewalls between Consul, Nginx, and Spring instances allow traffic on:
  • Consul’s HTTP port (8500)
  • Your Spring app’s port (e.g., 8080)
  • Nginx’s listening port (e.g., 80)
• For production, consider running Consul Template as a background service (using systemd on Linux) so it starts automatically on boot.

内容的提问来源于stack exchange，提问作者Ravat Tailor