Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 2 of 2 for listen (0.21 sec)

  1. docs/en/docs/advanced/behind-a-proxy.md

    Probably in many cases the default will be that the proxy doesn't have a stripped path prefix.
    
    In a case like that (without a stripped path prefix), the proxy would listen on something like `https://myawesomeapp.com`, and then if the browser goes to `https://myawesomeapp.com/api/v1/app` and your server (e.g. Uvicorn) listens on `http://127.0.0.1:8000` the proxy (without a stripped path prefix) would access Uvicorn at the same path: `http://127.0.0.1:8000/api/v1/app`.
    
    Plain Text
    - Registered: Sun May 05 07:19:11 GMT 2024
    - Last Modified: Thu May 02 22:37:31 GMT 2024
    - 11.6K bytes
    - Viewed (2)
  2. docs/en/docs/deployment/concepts.md

    * **Uvicorn** managing **Uvicorn workers**
        * One Uvicorn **process manager** would listen on the **IP** and **port**, and it would start **multiple Uvicorn worker processes**.
    * **Kubernetes** and other distributed **container systems**
        * Something in the **Kubernetes** layer would listen on the **IP** and **port**. The replication would be by having **multiple containers**, each with **one Uvicorn process** running.
    Plain Text
    - Registered: Sun May 05 07:19:11 GMT 2024
    - Last Modified: Thu May 02 22:37:31 GMT 2024
    - 18K bytes
    - Viewed (0)
Back to top