- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 109 for localhost (0.16 sec)
-
docs/sts/web-identity.md
``` $ go run web-identity.go -cid 204367807228-ok7601k6gj1pgge7m09h7d79co8p35xx.apps.googleusercontent.com -csec XsT_PgPdT1nO9DD45rMLJw7G 2018/12/26 17:49:36 listening on http://localhost:8080/ ```
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 19.2K bytes - Viewed (1) -
docs/config/README.md
``` KEY: etcd federate multiple clusters for IAM and Bucket DNS ARGS: endpoints* (csv) comma separated list of etcd endpoints e.g. "http://localhost:2379" path_prefix (path) namespace prefix to isolate tenants e.g. "customer1/" coredns_path (path) shared bucket DNS records, default is "/skydns"
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Sep 11 21:48:54 GMT 2023 - 17.7K bytes - Viewed (0) -
docs/site-replication/run-multi-site-minio-idp.sh
chmod +x mc fi minio server --config-dir /tmp/minio-internal --address ":9001" http://localhost:9001/tmp/minio-internal-idp1/{1...4} http://localhost:9010/tmp/minio-internal-idp1/{5...8} >/tmp/minio1_1.log 2>&1 & site1_pid1=$! minio server --config-dir /tmp/minio-internal --address ":9010" http://localhost:9001/tmp/minio-internal-idp1/{1...4} http://localhost:9010/tmp/minio-internal-idp1/{5...8} >/tmp/minio1_2.log 2>&1 & site1_pid2=$!
Shell Script - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Mar 07 00:19:24 GMT 2024 - 11.9K bytes - Viewed (0) -
docs/site-replication/run-multi-site-ldap.sh
site3_pid=$! sleep 10 export MC_HOST_minio1=http://minio:minio123@localhost:9001 export MC_HOST_minio2=http://minio:minio123@localhost:9002 export MC_HOST_minio3=http://minio:minio123@localhost:9003 ./mc admin replicate add minio1 minio2 minio3 ./mc idp ldap policy attach minio1 consoleAdmin --user="uid=dillon,ou=people,ou=swengg,dc=min,dc=io" sleep 5
Shell Script - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Feb 14 04:51:23 GMT 2024 - 10K bytes - Viewed (1) -
helm-releases/minio-2.0.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...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Aug 26 07:36:46 GMT 2021 - 13.6K bytes - Viewed (0) -
helm-releases/minio-1.0.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...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Aug 24 19:04:07 GMT 2021 - 13.6K bytes - Viewed (0) -
helm-releases/minio-3.3.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...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Dec 11 17:28:02 GMT 2021 - 14.6K bytes - Viewed (0) -
helm-releases/minio-3.1.4.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...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Sep 20 05:30:22 GMT 2021 - 14.4K bytes - Viewed (0) -
helm-releases/minio-3.4.4.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...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Dec 31 04:21:24 GMT 2021 - 15.2K bytes - Viewed (0) -
helm-releases/minio-3.5.2.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...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Feb 08 00:29:26 GMT 2022 - 15.4K bytes - Viewed (0)