- Sort Score
- Result 10 results
- Languages All
Results 291 - 300 of 552 for lport (0.03 sec)
-
docs/de/docs/deployment/manually.md
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 5.3K bytes - Viewed (0) -
docs/en/docs/advanced/behind-a-proxy.md
[entryPoints.http] address = ":9999" [providers] [providers.file] filename = "routes.toml" ``` This tells Traefik to listen on port 9999 and to use another file `routes.toml`. /// tip We are using port 9999 instead of the standard HTTP port 80 so that you don't have to run it with admin (`sudo`) privileges. /// Now create that other file `routes.toml`: ```TOML hl_lines="5 12 20"
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 27 16:49:49 UTC 2024 - 11.6K bytes - Viewed (0) -
.github/workflows/mint/minio-compress-encrypt.yaml
interval: 5s timeout: 5s retries: 5 # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: minio1: <<: *minio-common hostname: minio1 volumes: - cdata1-1:/cdata1 - cdata1-2:/cdata2 minio2: <<: *minio-common hostname: minio2 volumes:
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Fri Nov 03 21:18:18 UTC 2023 - 1.7K bytes - Viewed (0) -
.github/workflows/mint/minio-resiliency.yaml
interval: 5s timeout: 5s retries: 5 # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: minio1: <<: *minio-common hostname: minio1 volumes: - rdata1-1:/rdata1 - rdata1-2:/rdata2 minio2: <<: *minio-common hostname: minio2 volumes:
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Wed May 22 23:07:14 UTC 2024 - 1.7K bytes - Viewed (0) -
.github/workflows/multipart/docker-compose-site1.yaml
environment: - MINIO_PROMETHEUS_AUTH_TYPE=public - CI=true # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: site1-minio1: <<: *minio-common hostname: site1-minio1 volumes: - site1-data1-1:/data1 - site1-data1-2:/data2 site1-minio2: <<: *minio-common
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sat Sep 30 10:13:56 UTC 2023 - 1.5K bytes - Viewed (0) -
istioctl/pkg/admin/istiodconfig.go
if err != nil { return fmt.Errorf("could not build port forwarder for ControlZ %s: %v", podName, err) } defer portForwarder.Close() err = portForwarder.Start() if err != nil { return fmt.Errorf("could not start port forwarder for ControlZ %s: %v", podName, err) } ctrlzClient := &ControlzClient{ baseURL: &url.URL{
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Sat Apr 13 05:23:38 UTC 2024 - 13.5K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/internal/connection/RouteSelector.kt
socketHost = address.url.host socketPort = address.url.port } else { val proxyAddress = proxy.address() require(proxyAddress is InetSocketAddress) { "Proxy.address() is not an InetSocketAddress: ${proxyAddress.javaClass}" } socketHost = proxyAddress.socketHost socketPort = proxyAddress.port } if (socketPort !in 1..65535) {
Registered: Fri Nov 01 11:42:11 UTC 2024 - Last Modified: Wed Mar 06 17:33:38 UTC 2024 - 7.2K bytes - Viewed (0) -
docs/de/docs/deployment/concepts.md
Erinnern Sie sich aus der Dokumentation [Über HTTPS](https.md){.internal-link target=_blank}, dass nur ein Prozess auf einer Kombination aus Port und IP-Adresse auf einem Server lauschen kann? Das ist immer noch wahr. Um also **mehrere Prozesse** gleichzeitig zu haben, muss es einen **einzelnen Prozess geben, der einen Port überwacht**, welcher dann die Kommunikation auf irgendeine Weise an jeden Workerprozess überträgt. ### Arbeitsspeicher pro Prozess
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 20.6K bytes - Viewed (0) -
src/main/resources/fess_indices/fess_config.file_authentication/file_authentication.json
Registered: Thu Oct 31 13:40:30 UTC 2024 - Last Modified: Thu Dec 02 13:14:56 UTC 2021 - 644 bytes - Viewed (0) -
src/packaging/common/env/fess
FESS_TEMP_PATH=${packaging.fess.temp.dir} FESS_LOG_PATH=${packaging.fess.log.dir} FESS_CONF_PATH=${packaging.fess.conf.dir} FESS_VAR_PATH=${packaging.fess.var.dir} FESS_DICTIONARY_PATH=/var/lib/opensearch/config/ # Port FESS_PORT=8080 # Heap Memory FESS_HEAP_SIZE=512m # Elasticsearch Path SEARCH_ENGINE_HOME=/usr/share/opensearch/ # Elasticsearch URL
Registered: Thu Oct 31 13:40:30 UTC 2024 - Last Modified: Sun Jan 15 06:32:15 UTC 2023 - 489 bytes - Viewed (0)