Reverse proxy in Traefik with subdirectories.
Briefly

Traefik operates on a structured request flow, starting from entry points, then forwarding to routers and middleware before reaching backend services, which are typically Docker containers.
As each request is processed, Traefik adheres to specific criteria set at the router level, ensuring that requests are accurately mapped to the appropriate backend services based on the sub-directory of the URL.
The configuration involves setting up entry points where Traefik listens for incoming traffic, allowing for flexible routing based on user-defined conditions.
Middleware functions in Traefik play a crucial role, allowing for on-the-fly alterations of requests, such as path rewrites, enhancing how requests are routed to services.
Read at Medium
[
|
]