- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for locale (0.14 sec)
-
docs/es/docs/tutorial/first-steps.md
En el output, hay una línea que dice más o menos: ```hl_lines="4" INFO: Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit) ``` Esa línea muestra la URL dónde se está sirviendo tu app en tu maquina local. ### Revísalo Abre tu navegador en <a href="http://127.0.0.1:8000" class="external-link" target="_blank">http://127.0.0.1:8000</a>. Verás la respuesta en JSON: ```JSON {"message": "Hello World"} ```
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 9.9K bytes - Viewed (0) -
docs/en/docs/deployment/docker.md
Then, in that case, it could be simpler to have **one container** with **multiple processes**, and a local tool (e.g. a Prometheus exporter) on the same container collecting Prometheus metrics for all the internal processes and exposing those metrics on that single container. ---
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) -
docs/pt/docs/deployment/docker.md
Então, nesse caso, poderia ser mais simples ter **um único contêiner** com **múltiplos processos**, e uma ferramenta local (por exemplo, um exportador do Prometheus) no mesmo contêiner coletando métricas do Prometheus para todos os processos internos e expor essas métricas no único contêiner. ---
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 37.4K bytes - Viewed (0)