Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 8 of 8 for Jones (0.13 sec)

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

    #### Operation
    
    "Operation" here refers to one of the HTTP "methods".
    
    One of:
    
    * `POST`
    * `GET`
    * `PUT`
    * `DELETE`
    
    ...and the more exotic ones:
    
    * `OPTIONS`
    * `HEAD`
    * `PATCH`
    * `TRACE`
    
    In the HTTP protocol, you can communicate to each path using one (or more) of these "methods".
    
    ---
    
    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

    I'll tell you a bit more about these **concepts** here, and that would hopefully give you the **intuition** you would need to decide how to deploy your API in very different environments, possibly even in **future** ones that don't exist yet.
    
    By considering these concepts, you will be able to **evaluate and design** the best way to deploy **your own APIs**.
    
    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/release-notes.md

        * These `dependencies` are run before the normal parameter dependencies. And normal dependencies are run too. They can be combined.
        * Dependencies declared in a router are executed first, then the ones defined in *path operation decorators*, and then the ones declared in normal parameters. They are all combined and executed.
    Plain Text
    - Registered: Sun May 05 07:19:11 GMT 2024
    - Last Modified: Fri May 03 23:25:42 GMT 2024
    - 388.1K bytes
    - Viewed (1)
  4. docs/en/docs/advanced/openapi-callbacks.md

    So we are going to use that same knowledge to document how the *external API* should look like... by creating the *path operation(s)* that the external API should implement (the ones your API will call).
    
    !!! tip
        When writing the code to document a callback, it might be useful to imagine that you are that *external developer*. And that you are currently implementing the *external API*, not *your API*.
    
    Plain Text
    - Registered: Sun May 05 07:19:11 GMT 2024
    - Last Modified: Thu May 02 22:37:31 GMT 2024
    - 7.7K bytes
    - Viewed (0)
  5. README.md

    ```bash
    pip install fastapi
    ```
    
    ...it includes the same code and dependencies as:
    
    ```bash
    pip install "fastapi-slim[standard]"
    ```
    
    The standard extra dependencies are the ones mentioned above.
    
    ## License
    
    Plain Text
    - Registered: Sun May 05 07:19:11 GMT 2024
    - Last Modified: Thu May 02 22:37:31 GMT 2024
    - 22.6K bytes
    - Viewed (0)
  6. docs/en/docs/tutorial/index.md

    # Tutorial - User Guide
    
    This tutorial shows you how to use **FastAPI** with most of its features, step by step.
    
    Each section gradually builds on the previous ones, but it's structured to separate topics, so that you can go directly to any specific one to solve your specific API needs.
    
    It is also built to work as a future reference.
    
    So you can come back and see exactly what you need.
    
    ## Run the code
    
    Plain Text
    - Registered: Sun May 05 07:19:11 GMT 2024
    - Last Modified: Thu May 02 22:37:31 GMT 2024
    - 5.9K bytes
    - Viewed (0)
  7. docs/en/docs/index.md

    ```bash
    pip install fastapi
    ```
    
    ...it includes the same code and dependencies as:
    
    ```bash
    pip install "fastapi-slim[standard]"
    ```
    
    The standard extra dependencies are the ones mentioned above.
    
    ## License
    
    Plain Text
    - Registered: Sun May 05 07:19:11 GMT 2024
    - Last Modified: Thu May 02 22:37:31 GMT 2024
    - 19.8K bytes
    - Viewed (0)
  8. docs/en/docs/deployment/docker.md

    In this case, if you had **multiple containers**, by default, when Prometheus came to **read the metrics**, it would get the ones for **a single container each time** (for the container that handled that particular request), instead of getting the **accumulated metrics** for all the replicated containers.
    
    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