Set up reverse proxy patterns for routing traffic to backend services using Nginx, Traefik, or ShinyProxy.
| Configuration | Static files | Docker labels / dynamic | | Auto-discovery | No (manual) | Yes (Docker provider) | | Let's Encrypt | Via certbot | Built-in ACME | | Dashboard | No (3rd party) | Built-in | | WebSocket | Manual config | Automatic | | Best for | Static config, high traffic | Dynamic Docker environments |
Note: Trailing / on proxypass strips the location prefix. proxypass http://api:8000/; with location /api/ forwards /api/users as /users.
Configure reverse proxy patterns across multiple tools including Nginx, Traefik, and ShinyProxy. Covers WebSocket proxying, path-based and host-based routing, SSL termination, and Docker label auto-discovery. Use when routing multiple services behind a single entry point, proxying WebSocket connections (Shiny, Socket.IO), auto-discovering Docker services with Traefik labels, or adding SSL termination to services that don't handle TLS natively. Source: pjt222/development-guides.