Search Options

Results per page
Sort
Preferred Languages
Advance

Results 351 - 360 of 441 for Localhost (0.39 sec)

  2. github.com/minio/minio

    helm-releases/minio-3.5.9.tgz 

    .Values.service.type "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Thu Mar 03 23:29:03 UTC 2022
    - 17.7K bytes
    - Viewed (0)
  3. github.com/minio/minio

    helm-releases/minio-3.6.3.tgz 

    .Values.service.type "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Thu Mar 24 04:07:15 UTC 2022
    - 17.9K bytes
    - Viewed (0)
  4. github.com/minio/minio

    helm-releases/minio-3.1.9.tgz 

    .Values.service.type "ClusterIP" "NodePort" }} Minio can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access Minio from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sun Oct 10 21:28:04 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  5. github.com/minio/minio

    helm-releases/minio-3.3.0.tgz 

    .Values.service.type "ClusterIP" "NodePort" }} Minio can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access Minio from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Thu Nov 25 17:33:26 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  6. github.com/minio/minio

    helm-releases/minio-3.4.0.tgz 

    .Values.service.type "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sun Dec 19 22:32:49 UTC 2021
    - 14.8K bytes
    - Viewed (0)
  7. github.com/minio/minio

    helm-releases/minio-3.4.1.tgz 

    .Values.service.type "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Mon Dec 20 21:11:50 UTC 2021
    - 15.2K bytes
    - Viewed (0)
  8. github.com/codelibs/jcifs

    src/main/java/jcifs/netbios/NameServiceClientImpl.java 

                try {
                localInetAddress = InetAddress.getLocalHost();
            } catch (final UnknownHostException uhe) {
                /*
                 * Java cannot determine the localhost. This is basically a config
                 * issue on the host. There's not much we can do about it. Just
                 * to suppress NPEs that would result we can create a possibly bogus
    Registered: Sat Dec 20 13:44:44 UTC 2025
    - Last Modified: Sat Aug 30 05:58:03 UTC 2025
    - 38.5K bytes
    - Viewed (0)
  9. github.com/square/okhttp

    okhttp/src/jvmTest/kotlin/okhttp3/internal/connection/RouteSelectorTest.kt 

        assertThat(socketAddress.socketHost).isEqualTo("127.0.0.1")

    // InetAddress proxy specification.
    socketAddress = InetSocketAddress(InetAddress.getByName("localhost"), 1234)
    assertThat(socketAddress.socketHost).isEqualTo("127.0.0.1")
    socketAddress = InetSocketAddress(InetAddress.getByAddress(byteArrayOf(127, 0, 0, 1)), 1234)
    Registered: Fri Dec 26 11:42:13 UTC 2025
    - Last Modified: Wed Oct 08 03:50:05 UTC 2025
    - 20.3K bytes
    - Viewed (0)
  10. github.com/minio/minio

    docs/bucket/replication/setup_ilm_expiry_replication.sh 

    ./mc mb sitec/bucket

## Setup site replication
./mc admin replicate add sitea siteb --replicate-ilm-expiry

sleep 10s

## Add warm tier
./mc ilm tier add minio sitea WARM-TIER --endpoint http://localhost:9006 --access-key minio --secret-key minio123 --bucket bucket

## Add ILM rules
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Fri Sep 06 09:42:21 UTC 2024
    - 12.8K bytes
    - Viewed (0)
  11. github.com/tiangolo/fastapi

    docs/es/docs/advanced/behind-a-proxy.md 

    Si el cliente intenta ir a `/items`, por defecto, sería redirigido a `/items/`.

Pero antes de configurar la *Opción de CLI* `--forwarded-allow-ips` podría redirigir a `http://localhost:8000/items/`.

Pero quizá tu aplicación está alojada en `https://mysuperapp.com`, y la redirección debería ser a `https://mysuperapp.com/items/`.
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Dec 17 20:41:43 UTC 2025
    - 17.1K bytes
    - Viewed (0)
Back to top