- Sort Score
- Num 10 results
- Language All
Results 261 - 270 of 389 for localhost (0.08 seconds)
-
helm-releases/minio-1.0.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...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Aug 20 22:32:29 GMT 2021 - 13.5K bytes - Click Count (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...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Tue Aug 24 19:04:07 GMT 2021 - 13.6K bytes - Click Count (0) -
helm-releases/minio-1.0.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...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Wed Aug 25 02:12:51 GMT 2021 - 13.6K bytes - Click Count (0) -
helm-releases/minio-1.0.5.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...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Wed Aug 25 19:53:57 GMT 2021 - 13.6K bytes - Click Count (0) -
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...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Thu Aug 26 07:36:46 GMT 2021 - 13.6K bytes - Click Count (0) -
helm-releases/minio-3.6.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...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Tue Apr 12 01:30:28 GMT 2022 - 17.9K bytes - Click Count (0) -
docs/es/docs/advanced/generate-clients.md
### Hey API { #hey-api } Una vez que tenemos una app de FastAPI con los modelos, podemos usar Hey API para generar un cliente de TypeScript. La forma más rápida de hacerlo es con npx. ```sh npx @hey-api/openapi-ts -i http://localhost:8000/openapi.json -o src/client ``` Esto generará un SDK de TypeScript en `./src/client`.Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Wed Dec 17 20:41:43 GMT 2025 - 10.8K bytes - Click Count (0) -
cmd/local-locker.go
func (l *localLocker) getMutex() func() { l.waitMutex.Add(1) l.mutex.Lock() l.waitMutex.Add(-1) return l.mutex.Unlock } func (l *localLocker) String() string { return globalEndpoints.Localhost() } func (l *localLocker) canTakeLock(resources ...string) bool { for _, resource := range resources { _, lockTaken := l.lockMap[resource] if lockTaken { return false } } return true }
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Sep 28 20:59:21 GMT 2025 - 12K bytes - Click Count (0) -
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/`.
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Wed Dec 17 20:41:43 GMT 2025 - 16.4K bytes - Click Count (0) -
okhttp/src/jvmTest/kotlin/okhttp3/EventListenerTest.kt
Created: Fri Dec 26 11:42:13 GMT 2025 - Last Modified: Wed Nov 05 18:28:35 GMT 2025 - 70.5K bytes - Click Count (0)