- Sort Score
- Result 10 results
- Languages All
Results 301 - 310 of 486 for below (0.78 sec)
-
helm-releases/minio-3.1.6.tgz
"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 }} Read more about...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Thu Sep 23 19:56:39 UTC 2021 - 14.5K bytes - Viewed (0) -
LICENSE
can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below. When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge
Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Mon Jan 18 20:25:38 UTC 2016 - 25.8K bytes - Viewed (0) -
docs/en/docs/deployment/docker.md
Using Linux containers has several advantages including **security**, **replicability**, **simplicity**, and others. /// tip In a hurry and already know this stuff? Jump to the [`Dockerfile` below 👇](#build-a-docker-image-for-fastapi). /// <details> <summary>Dockerfile Preview 👀</summary> ```Dockerfile FROM python:3.9 WORKDIR /code COPY ./requirements.txt /code/requirements.txt
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Sat Sep 20 12:58:04 UTC 2025 - 29.5K bytes - Viewed (1) -
helm-releases/minio-1.0.0.tgz
"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 }} Read more about...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Fri Aug 20 22:30:54 UTC 2021 - 13.5K bytes - Viewed (0) -
helm-releases/minio-1.0.1.tgz
"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 }} Read more about...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Fri Aug 20 22:32:29 UTC 2021 - 13.5K bytes - Viewed (0) -
helm-releases/minio-1.0.3.tgz
"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 }} Read more about...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 24 19:04:07 UTC 2021 - 13.6K bytes - Viewed (0) -
helm-releases/minio-1.0.4.tgz
"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 }} Read more about...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Wed Aug 25 02:12:51 UTC 2021 - 13.6K bytes - Viewed (0) -
helm-releases/minio-1.0.5.tgz
"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 }} Read more about...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Wed Aug 25 19:53:57 UTC 2021 - 13.6K bytes - Viewed (0) -
helm-releases/minio-2.0.0.tgz
"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 }} Read more about...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Thu Aug 26 07:36:46 UTC 2021 - 13.6K bytes - Viewed (0) -
android/guava/src/com/google/common/base/Equivalence.java
* Equivalence<@Nullable Number>. That can still produce wrappers of various types -- * Wrapper<Number>, Wrapper<Integer>, Wrapper<@Nullable Integer>, etc. If we used just * Equivalence<? super T> below, no type could satisfy both that bound and T's own * bound. With this type, they have some overlap: in our example, Equivalence<Number> * and Equivalence<Object>. */
Registered: Fri Dec 26 12:43:10 UTC 2025 - Last Modified: Thu Jul 10 01:47:55 UTC 2025 - 14.5K bytes - Viewed (0)