Search Options

Results per page
Sort
Preferred Languages
Advance

Results 371 - 380 of 441 for Localhost (0.04 sec)

  2. github.com/minio/minio

    helm-releases/minio-4.0.10.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 Aug 04 16:09:22 UTC 2022
    - 19.2K bytes
    - Viewed (0)
  3. github.com/minio/minio

    helm-releases/minio-3.5.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: Wed Feb 02 00:16:41 UTC 2022
    - 15.2K bytes
    - Viewed (0)
  4. github.com/minio/minio

    helm-releases/minio-3.5.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: Fri Feb 04 22:54:20 UTC 2022
    - 15.4K bytes
    - Viewed (0)
  5. github.com/minio/minio

    helm-releases/minio-3.1.7.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 03 22:23:22 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  6. github.com/minio/minio

    helm-releases/minio-3.3.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: Thu Dec 02 20:09:18 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  7. github.com/minio/minio

    helm-releases/minio-3.6.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 Mar 13 22:44:21 UTC 2022
    - 17.9K bytes
    - Viewed (0)
  8. github.com/tiangolo/fastapi

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

    If the client tries to go to `/items`, by default, it would be redirected to `/items/`.

But before setting the *CLI Option* `--forwarded-allow-ips` it could redirect to `http://localhost:8000/items/`.

But maybe your application is hosted at `https://mysuperapp.com`, and the redirection should be to `https://mysuperapp.com/items/`.
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Dec 17 20:41:43 UTC 2025
    - 16.4K bytes
    - Viewed (0)
  9. github.com/minio/minio

    docs/resiliency/resiliency-tests.sh 

    }

function main() {
	if [ ! -f ./mc ]; then
		wget -q https://dl.minio.io/client/mc/release/linux-amd64/mc && chmod +x ./mc
	fi

	export MC_HOST_myminio=http://minioadmin:minioadmin@localhost:9000

	cleanup_and_prune

	# Run resiliency tests against MinIO
	docker compose -f "${DOCKER_COMPOSE_FILE}" up -d

	# Initial setup
	docs/resiliency/resiliency-initial-script.sh
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sat Dec 21 04:24:45 UTC 2024
    - 20.5K bytes
    - Viewed (0)
  10. github.com/codelibs/fess

    src/main/java/org/codelibs/fess/opensearch/client/SearchEngineClient.java 

                    try {
                    final InetAddress localhost = InetAddress.getByName("localhost");
                    httpAddress = IpAddressUtil.buildUrl("http", localhost, port, "");
                } catch (final UnknownHostException e) {
                    httpAddress = "http://localhost:" + port; // Fallback
                }
    Registered: Sat Dec 20 09:19:18 UTC 2025
    - Last Modified: Fri Nov 28 16:29:12 UTC 2025
    - 122.4K bytes
    - Viewed (1)
  11. github.com/tiangolo/fastapi

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

    Wenn der Client versucht, zu `/items` zu gehen, würde er standardmäßig zu `/items/` umgeleitet.

Aber bevor Sie die *CLI-Option* `--forwarded-allow-ips` setzen, könnte er zu `http://localhost:8000/items/` umleiten.

Aber möglicherweise wird Ihre Anwendung unter `https://mysuperapp.com` gehostet, und die Weiterleitung sollte zu `https://mysuperapp.com/items/` erfolgen.
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Dec 17 20:41:43 UTC 2025
    - 18.6K bytes
    - Viewed (0)
Back to top