nginx-proxy/nginx-proxy
Nginx Proxy
This project is an automated reverse proxy and load balancer designed for containerized environments. It functions by monitoring container lifecycle events through the container runtime API, allowing it to dynamically generate and update web server configurations in real time as services start, stop, or change their network status.
The system distinguishes itself through its ability to orchestrate proxy processes without dropping active connections, ensuring continuous availability during configuration updates. It utilizes a template-based engine to map container metadata to routing logic, enabling complex traffic distribution across multiple service instances based on hostnames or URL path prefixes.
Beyond core routing, the project provides a comprehensive suite of traffic management and security capabilities. It handles SSL and TLS termination at the proxy layer to offload cryptographic overhead from backend services and supports automated certificate management. Additionally, it enforces network access controls and client authentication to secure services within isolated environments.
The software is configured through environment variables, container labels, and external configuration files, providing flexibility for diverse application requirements.
Features
- Reverse Proxies - Automatically generates proxy configurations by monitoring Docker lifecycle events for service discovery.
- Load Balancers - Distributes incoming traffic across multiple containers sharing the same virtual host by applying configurable algorithms to ensure even workload distribution.
- Host-Based Matchers - Directs incoming requests to specific containers based on virtual host names, supporting complex matching patterns like wildcards and regular expressions.
- Path-Based Routers - Directs requests to different containers based on URL path prefixes, allowing multiple independent services to share a single domain name.
- SSL/TLS Certificate Management - Handles encrypted traffic by automating certificate management and offloading secure connections for backend services.
- Container Orchestration Tools - Manages network traffic routing and load balancing for services running within isolated container environments.
- Docker Socket Orchestrators - Interacts with the local container daemon socket to programmatically detect lifecycle changes and trigger updates.
- SSL Termination Proxies - Handles SSL and TLS handshake termination at the proxy layer to offload cryptographic overhead.
- Proxy and Infrastructure - Automated proxy configuration for Docker container environments.
- Reverse Proxies - Automated reverse proxy configuration for containers.
- Container Management - Automated reverse proxy configuration for Docker containers.
- Domain Traffic Filters - Directs traffic to different backend services based on hostnames or URL paths to host multiple applications on one domain.
- Host Header Matchers - Maps incoming HTTP request headers to specific backend container endpoints based on domain names and URL path prefixes.
- Reverse Proxy Orchestrators - Orchestrates long-running proxy processes that reload routing tables dynamically without dropping active connections.
- Configuration-Driven Templating Engines - Uses a templating engine to transform container metadata into valid server configuration files during runtime.
- Client Certificate Authentication - Verifies incoming traffic using basic authentication or client certificates to ensure only authorized access.
- Network Access Controls - Restricts access to sensitive services by isolating containers and enforcing authentication for incoming traffic.
- Proxy Configurations - Allows overriding default proxy behavior through custom configuration files, environment variables, and container labels.
Star history
How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.
