Deploying to gh-pages from @ litestar-org/litestar@4a43322 🚀

Author: aaron-gheevarghese

4897/_modules/litestar/handlers/base.html

@@ -13,7 +13,7 @@ Methodology
 - Tests for the frameworks are written to make them as comparable as possible while
   completing the same tasks (you can see them
   `here <https://github.com/litestar-org/api-performance-tests/tree/main/frameworks>`__)
-- Each application is run using `uvicorn <https://www.uvicorn.org/>`__ with
+- Each application is run using `uvicorn <https://uvicorn.dev/>`__ with
   **one worker** and `uvloop <https://uvloop.readthedocs.io/>`__
 - Test data has been randomly generated and is being imported from a shared module
 - All frameworks are used with their "stock" configuration, i.e. without applying any

4897/_sources/benchmarks.rst

@@ -211,7 +211,7 @@ entry-point and pass it to Litestar:
 
    app = Litestar(route_handlers=[UserController])
 
-To **run your application**, use an ASGI server such as `uvicorn <https://www.uvicorn.org/>`_ :
+To **run your application**, use an ASGI server such as `uvicorn <https://uvicorn.dev/>`_ :
 
 .. code-block:: shell
 

4897/_sources/getting-started.rst

@@ -1330,7 +1330,7 @@
         additional validation was added to generate a more user friendly CLI errors.
 
         The other SSL-related flags (like password or CA) were not added (yet). See
-        `uvicorn CLI docs <https://www.uvicorn.org/#command-line-options>`_
+        `uvicorn CLI docs <https://uvicorn.dev/#command-line-options>`_
 
         **Generating of a self-signed certificate**
 

4897/_sources/release-notes/2.x-changelog.rst

@@ -37,7 +37,7 @@ Choosing an ASGI Server
     .. tab-item:: Uvicorn
         :sync: uvicorn
 
-        `Uvicorn <https://www.uvicorn.org/>`_ is an ASGI server that supports ``HTTP/1.1`` and WebSocket.
+        `Uvicorn <https://uvicorn.dev/>`_ is an ASGI server that supports ``HTTP/1.1`` and WebSocket.
 
     .. tab-item:: Hypercorn
         :sync: hypercorn

4897/_sources/topics/deployment/manually-with-asgi-server.rst

@@ -49,7 +49,7 @@ However, it gets tricky quickly. For example, if the same route handler would be
 included in a router with a path parameter with the name ``message``, the path parameter
 would win, and ``message`` wouldn't be a query parameter anymore.
 
-This means that the inferred parameter source is context dependant.
+This means that the inferred parameter source is context dependent.
 
 There are upsides to this, for example, one could argue that this is a practical
 application of the
@@ -98,7 +98,7 @@ for nuance".
 This is easy to write, or rather, easy to type. However, there's not much information
 available to a reader. Where do ``data`` and all the other parameters come from? One
 could infer from ``limit`` and ``page`` that they're probably query parameters, but as
-discussed in `Historical background`_, that could also be context dependant.
+discussed in `Historical background`_, that could also be context dependent.
 
 
 **Easy to read**

4897/_sources/topics/explicit_declarations.rst

@@ -11,7 +11,7 @@ Install Litestar
 ++++++++++++++++
 
 To install Litestar, run ``pip install 'litestar[standard]'``. This will install Litestar
-as well as `uvicorn <https://www.uvicorn.org/>`_ -  a web server to serve your application.
+as well as `uvicorn <https://uvicorn.dev/>`_ -  a web server to serve your application.
 
 .. note::
     You can use any ASGI-capable web server, but this tutorial will use - and Litestar
@@ -147,7 +147,7 @@ The last step is to actually run the application. Litestar does not include its
 server, but instead makes use of the
 `ASGI protocol <https://asgi.readthedocs.io>`_, which is a protocol Python objects can
 use in order to interact with application servers like
-`uvicorn <https://www.uvicorn.org/>`_ that actually implement the HTTP protocol and
+`uvicorn <https://uvicorn.dev/>`_ that actually implement the HTTP protocol and
 handle it for you.
 
 If you installed Litestar with ``pip install 'litestar[standard]'``, this will have

4897/_sources/tutorials/todo-app/0-application-basics.rst

@@ -74,7 +74,7 @@ receives data of a ``TodoItem`` the same way as the ``POST`` handler.
 
 An instance of ``Litestar`` is created, including the previously defined route handlers.
 This app can now be served using an ASGI server like
-`uvicorn <https://www.uvicorn.org/>`_, which can be conveniently done using Litestar's
+`uvicorn <https://uvicorn.dev/>`_, which can be conveniently done using Litestar's
 CLI by executing the ``litestar run`` command.
 
 

4897/_sources/tutorials/todo-app/3-assembling-the-app.rst

@@ -32,7 +32,7 @@ Startup and Shutdown
 You can pass a list of :term:`callables <python:callable>` - either sync or async functions, methods, or class instances
 - to the :paramref:`~litestar.app.Litestar.on_startup` / :paramref:`~litestar.app.Litestar.on_shutdown`
 :term:`kwargs <argument>` of the :class:`app <litestar.app.Litestar>` instance. Those will be called in
-order, once the ASGI server such as `uvicorn <https://www.uvicorn.org/>`_,
+order, once the ASGI server such as `uvicorn <https://uvicorn.dev/>`_,
 `Hypercorn <https://hypercorn.readthedocs.io/en/latest/#/>`_, `Granian <https://github.com/emmett-framework/granian/>`_,
 `Daphne <https://github.com/django/daphne/>`_, etc. emits the respective event.
 

4897/_sources/usage/applications.rst

@@ -2,7 +2,7 @@ CLI
 ===
 
 .. |uvicorn| replace:: uvicorn
-.. _uvicorn: https://www.uvicorn.org/
+.. _uvicorn: https://uvicorn.dev/
 
 Litestar provides a convenient command line interface (CLI) for running and managing Litestar applications. The CLI is
 powered by `click <https://click.palletsprojects.com/>`_, `rich <https://rich.readthedocs.io>`_,