- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 22 for Ip (0.12 sec)
-
architecture/ambient/ztunnel.md
* In Istio sidecars, historically we had a lot of client-specific xDS. For example, putting the xDS-client's IP back into the xDS response. This makes efficient control plane implementation (most notably, caching), extremely challenging. * In practice, this largely means that references are fully qualified in the API. IP Addresses (generally) have a network associated with them, node names have a cluster associated with them, etc.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Apr 25 22:35:16 GMT 2024 - 16.6K bytes - Viewed (0) -
docs/en/docs/fastapi-cli.md
By default it will listen on the IP address `127.0.0.1`, which is the IP for your machine to communicate with itself alone (`localhost`). ## `fastapi run` When you run `fastapi run`, it will run on production mode by default. It will have **auto-reload disabled** by default.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri May 03 23:25:16 GMT 2024 - 6.1K bytes - Viewed (0) -
docs/en/docs/deployment/concepts.md
Here are some possible combinations and strategies: * **Gunicorn** managing **Uvicorn workers** * Gunicorn would be the **process manager** listening on the **IP** and **port**, the replication would be by having **multiple Uvicorn worker processes**.
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) -
istioctl/pkg/writer/ztunnel/configdump/testdata/workloadsummary_default.txt
NAMESPACE POD NAME IP NODE WAYPOINT PROTOCOL default details-v1-698d88b-krdw7 10.244.2.55 ambient-worker2 None HBONE default httpbin-7447985f87-t8hv7 10.244.1.40 ambient-worker None TCP default productpage-v1-675fc69cf-kkrm2 10.244.2.56 ambient-worker2 None HBONE default ratings-v1-6484c4d9bb-8xc2r 10.244.2.57 ambient-worker2 None HBONE
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 23 21:30:30 GMT 2024 - 757 bytes - Viewed (0) -
docs/ru/docs/deployment/concepts.md
Вот некоторые возможные комбинации и стратегии: * **Gunicorn** управляющий **воркерами Uvicorn**
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 32.5K bytes - Viewed (0) -
docs/zh/docs/deployment/server-workers.md
* `--worker-class`:在worker进程中使用的与 Gunicorn 兼容的工作类。 * 这里我们传递了 Gunicorn 可以导入和使用的类: ```Python import uvicorn.workers.UvicornWorker ``` * `--bind`:这告诉 Gunicorn 要监听的 IP 和端口,使用冒号 (`:`) 分隔 IP 和端口。 * 如果您直接运行 Uvicorn,则可以使用`--host 0.0.0.0`和`--port 80`,而不是`--bind 0.0.0.0:80`(Gunicorn 选项)。 在输出中,您可以看到它显示了每个进程的 **PID**(进程 ID)(它只是一个数字)。 你可以看到:
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 8.7K bytes - Viewed (0) -
docs/zh/docs/deployment/concepts.md
可以通过多种方法来实现这一目标,我将在接下来的章节中向您详细介绍具体策略,例如在谈论 Docker 和容器时。 要考虑的主要限制是必须有一个**单个**组件来处理**公共IP**中的**端口**。 然后它必须有一种方法将通信**传输**到复制的**进程/worker**。 以下是一些可能的组合和策略: * **Gunicorn** 管理 **Uvicorn workers** * Gunicorn 将是监听 **IP** 和 **端口** 的 **进程管理器**,复制将通过 **多个 Uvicorn 工作进程** 进行 * **Uvicorn** 管理 **Uvicorn workers** * 一个 Uvicorn **进程管理器** 将监听 **IP** 和 **端口**,并且它将启动 **多个 Uvicorn 工作进程** * **Kubernetes** 和其他分布式 **容器系统**
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 16.2K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/Dispatcher.kt
} /** * The maximum number of requests for each host to execute concurrently. This limits requests by * the URL's host name. Note that concurrent requests to a single IP address may still exceed this * limit: multiple hostnames may share an IP address or be routed through the same HTTP proxy. * * If more than [maxRequestsPerHost] requests are in flight when this is invoked, those requests * will remain in flight. *
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Sat Apr 20 17:03:43 GMT 2024 - 9K bytes - Viewed (0) -
docs/en/docs/deployment/server-workers.md
* Here we pass the class that Gunicorn can import and use with: ```Python import uvicorn.workers.UvicornWorker ``` * `--bind`: This tells Gunicorn the IP and the port to listen to, using a colon (`:`) to separate the IP and the port. * If you were running Uvicorn directly, instead of `--bind 0.0.0.0:80` (the Gunicorn option) you would use `--host 0.0.0.0` and `--port 80`.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 9.1K bytes - Viewed (0) -
cni/README.md
## Reference
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri May 03 19:29:42 GMT 2024 - 12.3K bytes - Viewed (0)