- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 24 for focus (0.16 sec)
-
docs/en/docs/advanced/websockets.md
This, of course, is not optimal and you wouldn't use it for production. In production you would have one of the options above. But it's the simplest way to focus on the server-side of WebSockets and have a working example: ```Python hl_lines="2 6-38 41-43" {!../../../docs_src/websockets/tutorial001.py!} ``` ## Create a `websocket`
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 6.2K bytes - Viewed (0) -
docs/en/docs/alternatives.md
But then, the project's focus shifted. It was no longer an API web framework, as the creator needed to focus on Starlette. Now APIStar is a set of tools to validate OpenAPI specifications, not a web framework. !!! info
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 23.2K bytes - Viewed (0) -
docs/en/docs/deployment/https.md
!!! tip This Domain Name part is way before HTTPS, but as everything depends on the domain and the IP address, it's worth mentioning it here. ### DNS Now let's focus on all the actual HTTPS parts. First, the browser would check with the **DNS servers** what is the **IP for the domain**, in this case, `someapp.example.com`.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Jan 11 16:31:18 GMT 2024 - 12K bytes - Viewed (0) -
docs/en/docs/tutorial/security/simple-oauth2.md
!!! tip In the next chapter, you will see a real secure implementation, with password hashing and <abbr title="JSON Web Tokens">JWT</abbr> tokens. But for now, let's focus on the specific details we need. === "Python 3.10+" ```Python hl_lines="87" {!> ../../../docs_src/security/tutorial003_an_py310.py!} ``` === "Python 3.9+"
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 12.5K bytes - Viewed (0) -
docs/en/docs/help-fastapi.md
* If the PR can be simplified in a way, you can ask for that, but there's no need to be too picky, there might be a lot of subjective points of view (and I will have my own as well 🙈), so it's better if you can focus on the fundamental things. ### Tests * Help me check that the PR has **tests**. * Check that the tests **fail** before the PR. 🚨 * Then check that the tests **pass** after the PR. ✅
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 13.7K bytes - Viewed (0) -
docs/en/docs/deployment/concepts.md
So let's focus on the main cases, where it could crash entirely in some particular cases **in the future**, and it still makes sense to restart it.
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) -
architecture/networking/pilot.md
In addition to this conversion, `Ingress` requires writing the address it can be reached at in status. This is done by the Ingress Status controller. #### Gateway
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Feb 07 17:53:24 GMT 2024 - 19.1K bytes - Viewed (0) -
docs/en/docs/how-to/sql-databases-peewee.md
We are going to create the same application as in the SQLAlchemy tutorial ([SQL (Relational) Databases](../tutorial/sql-databases.md){.internal-link target=_blank}). Most of the code is actually the same. So, we are going to focus only on the differences. ## File structure Let's say you have a directory named `my_super_project` that contains a sub-directory called `sql_app` with a structure like this: ``` . └── sql_app
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Tue Jan 16 13:23:25 GMT 2024 - 23.6K bytes - Viewed (1) -
docs/en/docs/deployment/docker.md
* HTTPS * Running on startup * Restarts * Replication (the number of processes running) * Memory * Previous steps before starting ## HTTPS If we focus just on the **container image** for a FastAPI application (and later the running **container**), HTTPS normally would be handled **externally** by another tool.
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) -
CHANGELOG/CHANGELOG-1.8.md
### SIG Autoscaling [SIG Autoscaling][] is responsible for autoscaling-related components, such as the Horizontal Pod Autoscaler and Cluster Autoscaler. For the 1.8 release, SIG Autoscaling continued to focus on stabilizing features introduced in previous releases: the new version of the Horizontal Pod Autoscaler API, which supports custom metrics, and the Cluster Autoscaler, which provides improved performance and error reporting.
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Tue Feb 20 15:45:02 GMT 2024 - 312.2K bytes - Viewed (1)