- Sort Score
- Result 10 results
- Languages All
Results 351 - 360 of 1,928 for post (0.06 sec)
-
helm-releases/minio-3.5.6.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 Nov 03 19:28:11 UTC 2024 - Last Modified: Sat Feb 19 20:34:14 UTC 2022 - 17.6K bytes - Viewed (0) -
helm-releases/minio-3.5.9.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 Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Mar 03 23:29:03 UTC 2022 - 17.7K bytes - Viewed (0) -
helm-releases/minio-3.4.6.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 Nov 03 19:28:11 UTC 2024 - Last Modified: Sat Jan 08 06:24:06 UTC 2022 - 15.2K bytes - Viewed (0) -
helm-releases/minio-3.4.8.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 Nov 03 19:28:11 UTC 2024 - Last Modified: Fri Jan 28 18:33:38 UTC 2022 - 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 }}...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Tue Feb 08 00:29:26 UTC 2022 - 15.4K bytes - Viewed (0) -
helm-releases/minio-3.1.8.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 Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Oct 07 05:03:47 UTC 2021 - 14.6K bytes - Viewed (0) -
docs/zh/docs/tutorial/first-steps.md
#### 操作 这里的「操作」指的是一种 HTTP「方法」。 下列之一: * `POST` * `GET` * `PUT` * `DELETE` ...以及更少见的几种: * `OPTIONS` * `HEAD` * `PATCH` * `TRACE` 在 HTTP 协议中,你可以使用以上的其中一种(或多种)「方法」与每个路径进行通信。 --- 在开发 API 时,你通常使用特定的 HTTP 方法去执行特定的行为。 通常使用: * `POST`:创建数据。 * `GET`:读取数据。 * `PUT`:更新数据。 * `DELETE`:删除数据。
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 9.1K bytes - Viewed (0) -
docs_src/path_operation_configuration/tutorial002.py
app = FastAPI() class Item(BaseModel): name: str description: Union[str, None] = None price: float tax: Union[float, None] = None tags: Set[str] = set() @app.post("/items/", response_model=Item, tags=["items"]) async def create_item(item: Item): return item @app.get("/items/", tags=["items"]) async def read_items(): return [{"name": "Foo", "price": 42}]
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sat May 14 11:59:59 UTC 2022 - 580 bytes - Viewed (0) -
docs/tr/docs/tutorial/first-steps.md
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 10.5K bytes - Viewed (0) -
android/guava-testlib/pom.xml
</plugin> <plugin> <artifactId>maven-source-plugin</artifactId> <executions> <execution> <id>attach-test-sources</id> <phase>post-integration-test</phase> <goals><goal>test-jar</goal></goals> </execution> </executions> </plugin> <plugin> <artifactId>maven-jar-plugin</artifactId>
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Wed Jul 24 18:53:31 UTC 2024 - 3.3K bytes - Viewed (0)