Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for Sharpe (0.14 sec)

  1. docs/en/docs/tutorial/first-steps.md

    #### Define a *path operation decorator*
    
    ```Python hl_lines="6"
    {!../../../docs_src/first_steps/tutorial001.py!}
    ```
    
    The `@app.get("/")` tells **FastAPI** that the function right below is in charge of handling requests that go to:
    
    * the path `/`
    * using a <abbr title="an HTTP GET method"><code>get</code> operation</abbr>
    
    !!! info "`@decorator` Info"
    Plain Text
    - Registered: Sun May 05 07:19:11 GMT 2024
    - Last Modified: Thu May 02 22:37:31 GMT 2024
    - 12K bytes
    - Viewed (0)
  2. docs/en/docs/deployment/concepts.md

    We also saw that HTTPS is normally provided by a component **external** to your application server, a **TLS Termination Proxy**.
    
    And there has to be something in charge of **renewing the HTTPS certificates**, it could be the same component or it could be something different.
    
    ### Example Tools for HTTPS
    
    Some of the tools you could use as a TLS Termination Proxy are:
    
    * Traefik
    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)
  3. docs/en/docs/deployment/docker.md

    Alternatively, HTTPS could be handled by a cloud provider as one of their services (while still running the application in a container).
    
    ## Running on Startup and Restarts
    
    There is normally another tool in charge of **starting and running** your container.
    
    It could be **Docker** directly, **Docker Compose**, **Kubernetes**, a **cloud service**, etc.
    
    Plain Text
    - Registered: Sun May 05 07:19:11 GMT 2024
    - Last Modified: Thu May 02 22:37:31 GMT 2024
    - 34K bytes
    - Viewed (0)
Back to top