Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 851 - 860 of 1,111 for client (0.04 seconds)

  1. .github/workflows/multipart/migrate.sh

    	docker system prune -f || true
    	docker volume prune -f || true
    	docker volume rm $(docker volume ls -q -f dangling=true) || true
    }
    
    cleanup
    
    if [ ! -f ./mc ]; then
    	wget --quiet -O mc https://dl.minio.io/client/mc/release/linux-amd64/mc &&
    		chmod +x mc
    fi
    
    export RELEASE=RELEASE.2023-08-29T23-07-35Z
    
    docker-compose -f docker-compose-site1.yaml up -d
    docker-compose -f docker-compose-site2.yaml up -d
    
    sleep 30s
    
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Mon May 27 19:17:46 GMT 2024
    - 4.3K bytes
    - Click Count (0)
  2. cmd/http-tracer.go

    			HTTP: &madmin.TraceHTTPStats{
    				ReqInfo: madmin.TraceRequestInfo{
    					Time:     reqStartTime,
    					Proto:    r.Proto,
    					Method:   r.Method,
    					RawQuery: redactLDAPPwd(r.URL.RawQuery),
    					Client:   handlers.GetSourceIP(r),
    					Headers:  reqHeaders,
    					Path:     reqPath,
    					Body:     reqRecorder.Data(),
    				},
    				RespInfo: madmin.TraceResponseInfo{
    					Time:       reqEndTime,
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Tue Sep 24 17:13:00 GMT 2024
    - 6K bytes
    - Click Count (0)
  3. cmd/bucket-encryption-handlers.go

    		return
    	}
    
    	configData, err := xml.Marshal(config)
    	if err != nil {
    		writeErrorResponse(ctx, w, toAPIError(ctx, err), r.URL)
    		return
    	}
    
    	// Write bucket encryption configuration to client
    	writeSuccessResponseXML(w, configData)
    }
    
    // DeleteBucketEncryptionHandler - Removes bucket encryption configuration
    func (api objectAPIHandlers) DeleteBucketEncryptionHandler(w http.ResponseWriter, r *http.Request) {
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Fri May 24 23:05:23 GMT 2024
    - 6.4K bytes
    - Click Count (0)
  4. helm-releases/minio-4.0.5.tgz

    about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/kubectl_port-forward/ You can now access MinIO server on http://localhost:9000. Follow the below steps to connect to MinIO server with mc client: 1. Download the MinIO mc client - https://docs.minio.io/docs/minio-client-quickstart-guide 2. export MC_HOST_{{ template "minio.fullname" . }}-local=http://$(kubectl get secret --namespace {{ .Release.Namespace }} {{ template "minio.secretName" . }} -o jsonpath="{.data.rootUser}" | base64...
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Sat Jul 16 06:42:56 GMT 2022
    - 18.3K bytes
    - Click Count (0)
  5. helm-releases/minio-4.0.8.tgz

    about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/kubectl_port-forward/ You can now access MinIO server on http://localhost:9000. Follow the below steps to connect to MinIO server with mc client: 1. Download the MinIO mc client - https://docs.minio.io/docs/minio-client-quickstart-guide 2. export MC_HOST_{{ template "minio.fullname" . }}-local=http://$(kubectl get secret --namespace {{ .Release.Namespace }} {{ template "minio.secretName" . }} -o jsonpath="{.data.rootUser}" | base64...
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Fri Jul 29 23:39:54 GMT 2022
    - 18.6K bytes
    - Click Count (0)
  6. helm-releases/minio-5.0.11.tgz

    .Release.Namespace }} Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/kubectl_port-forward/ You can now access MinIO server on http://localhost:9000. Follow the below steps to connect to MinIO server with mc client: 1. Download the MinIO mc client - https://min.io/docs/minio/linux/reference/minio-mc.html#quickstart 2. export MC_HOST_{{ template "minio.fullname" . }}-local=http://$(kubectl get secret --namespace {{ .Release.Namespace }} {{ template "minio.secretName" . }} -o...
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Wed Jun 21 19:29:09 GMT 2023
    - 20.3K bytes
    - Click Count (0)
  7. helm-releases/minio-5.0.12.tgz

    .Release.Namespace }} Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/kubectl_port-forward/ You can now access MinIO server on http://localhost:9000. Follow the below steps to connect to MinIO server with mc client: 1. Download the MinIO mc client - https://min.io/docs/minio/linux/reference/minio-mc.html#quickstart 2. export MC_HOST_{{ template "minio.fullname" . }}-local=http://$(kubectl get secret --namespace {{ .Release.Namespace }} {{ template "minio.secretName" . }} -o...
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Fri Jul 07 16:44:16 GMT 2023
    - 20.4K bytes
    - Click Count (0)
  8. helm-releases/minio-5.0.13.tgz

    .Release.Namespace }} Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/kubectl_port-forward/ You can now access MinIO server on http://localhost:9000. Follow the below steps to connect to MinIO server with mc client: 1. Download the MinIO mc client - https://min.io/docs/minio/linux/reference/minio-mc.html#quickstart 2. export MC_HOST_{{ template "minio.fullname" . }}-local=http://$(kubectl get secret --namespace {{ .Release.Namespace }} {{ template "minio.secretName" . }} -o...
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Sun Jul 09 07:13:05 GMT 2023
    - 20.3K bytes
    - Click Count (0)
  9. helm-releases/minio-5.0.7.tgz

    .Release.Namespace }} Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/kubectl_port-forward/ You can now access MinIO server on http://localhost:9000. Follow the below steps to connect to MinIO server with mc client: 1. Download the MinIO mc client - https://min.io/docs/minio/linux/reference/minio-mc.html#quickstart 2. export MC_HOST_{{ template "minio.fullname" . }}-local=http://$(kubectl get secret --namespace {{ .Release.Namespace }} {{ template "minio.secretName" . }} -o...
    Created: Sun Dec 28 19:28:13 GMT 2025
    - Last Modified: Mon Feb 13 10:37:23 GMT 2023
    - 20.3K bytes
    - Click Count (0)
  10. docs/en/docs/tutorial/background-tasks.md

    # Background Tasks { #background-tasks }
    
    You can define background tasks to be run *after* returning a response.
    
    This is useful for operations that need to happen after a request, but that the client doesn't really have to be waiting for the operation to complete before receiving the response.
    
    This includes, for example:
    
    * Email notifications sent after performing an action:
    Created: Sun Dec 28 07:19:09 GMT 2025
    - Last Modified: Wed Dec 17 20:41:43 GMT 2025
    - 4.8K bytes
    - Click Count (0)
Back to Top