Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 231 - 240 of 2,028 for post (0.03 seconds)

  2. github.com/tiangolo/fastapi

    docs/en/docs/tutorial/first-steps.md 

    ///

While building an API, the "path" is the main way to separate "concerns" and "resources".

#### Operation { #operation }

"Operation" here refers to one of the HTTP "methods".

One of:

* `POST`
* `GET`
* `PUT`
* `DELETE`

...and the more exotic ones:

* `OPTIONS`
* `HEAD`
* `PATCH`
* `TRACE`
    Created: Sun Apr 05 07:19:11 GMT 2026
    - Last Modified: Sat Mar 07 09:29:03 GMT 2026
    - 13.4K bytes
    - Click Count (0)
  3. github.com/tiangolo/fastapi

    docs/de/docs/tutorial/first-steps.md 

    #### Operation { #operation }

„Operation“ bezieht sich hier auf eine der HTTP-„Methoden“.

Eine von diesen:

* `POST`
* `GET`
* `PUT`
* `DELETE`

... und die etwas Exotischeren:

* `OPTIONS`
* `HEAD`
* `PATCH`
* `TRACE`
    Created: Sun Apr 05 07:19:11 GMT 2026
    - Last Modified: Thu Mar 19 17:58:09 GMT 2026
    - 14.9K bytes
    - Click Count (0)
  4. github.com/golang/go

    src/cmd/asm/internal/asm/testdata/arm64error.s 

    	VST1.P	[V4.S4,V5.S4], 48(R1)                            // ERROR "invalid post-increment offset"
	VST1.P	[V4.S4], 8(R1)                                   // ERROR "invalid post-increment offset"
	VLD1.P	32(R1), [V8.S4, V9.S4, V10.S4]                   // ERROR "invalid post-increment offset"
	VLD1.P	48(R1), [V7.S4, V8.S4, V9.S4, V10.S4]            // ERROR "invalid post-increment offset"
    Created: Tue Apr 07 11:13:11 GMT 2026
    - Last Modified: Tue Feb 24 21:29:25 GMT 2026
    - 38.5K bytes
    - Click Count (0)
  5. github.com/minio/minio

    helm-releases/minio-1.0.2.tgz 

    matchLabels: app: {{ template "minio.name" . }} {{- end }} minio/templates/post-install-create-bucket-job.yaml {{- if .Values.buckets }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-make-bucket-job labels: app: {{ template "minio.name" . }}-make-bucket-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations: "helm.sh/hook": post-install,post-upgrade "helm.sh/hook-delete-policy": hook-succeeded,before-hook-creation...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Tue Aug 24 18:58:05 GMT 2021
    - 13.6K bytes
    - Click Count (0)
  6. github.com/minio/minio

    helm-releases/minio-3.3.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 }}...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Sat Dec 11 17:26:01 GMT 2021
    - 14.6K bytes
    - Click Count (0)
  7. github.com/minio/minio

    helm-releases/minio-3.3.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 Apr 05 19:28:12 GMT 2026
    - Last Modified: Sat Dec 11 17:59:34 GMT 2021
    - 14.6K bytes
    - Click Count (0)
  8. github.com/minio/minio

    helm-releases/minio-3.4.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 }}...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Tue Dec 21 02:58:25 GMT 2021
    - 15.2K bytes
    - Click Count (0)
  9. github.com/minio/minio

    helm-releases/minio-3.5.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 Apr 05 19:28:12 GMT 2026
    - Last Modified: Sun Feb 13 23:43:44 GMT 2022
    - 15.4K bytes
    - Click Count (0)
  10. github.com/minio/minio

    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 }}...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Fri Dec 31 04:21:24 GMT 2021
    - 15.2K bytes
    - Click Count (0)
  11. github.com/minio/minio

    helm-releases/minio-3.4.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 Apr 05 19:28:12 GMT 2026
    - Last Modified: Wed Jan 05 19:32:55 GMT 2022
    - 15.2K bytes
    - Click Count (0)
Back to Top