- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 530 for xport (0.02 sec)
-
docs/chroot/README.md
- Chroot installed on your machine. ## 2. Install MinIO in Chroot ```sh mkdir -p /mnt/export/${USER}/bin wget https://dl.min.io/server/minio/release/linux-amd64/minio -O /mnt/export/${USER}/bin/minio chmod +x /mnt/export/${USER}/bin/minio ``` Bind your `proc` mount to the target chroot directory ``` sudo mount --bind /proc /mnt/export/${USER}/proc ``` ## 3. Run Standalone MinIO in Chroot ### GNU/Linux ```sh
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 1.8K bytes - Viewed (0) -
helm-releases/minio-1.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 }}...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Fri Aug 20 22:30:54 UTC 2021 - 13.5K bytes - Viewed (0) -
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 }}...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Fri Aug 20 22:32:29 UTC 2021 - 13.5K bytes - Viewed (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 }}...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Tue Aug 24 19:04:07 UTC 2021 - 13.6K bytes - Viewed (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 }}...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Wed Aug 25 02:12:51 UTC 2021 - 13.6K bytes - Viewed (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 }}...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Wed Aug 25 19:53:57 UTC 2021 - 13.6K bytes - Viewed (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 }}...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Thu Aug 26 07:36:46 UTC 2021 - 13.6K bytes - Viewed (0) -
docs/sts/ldap.md
``` export MINIO_ROOT_USER=minio export MINIO_ROOT_PASSWORD=minio123 export MINIO_IDENTITY_LDAP_SERVER_ADDR='my.ldap-active-dir-server.com:636' export MINIO_IDENTITY_LDAP_LOOKUP_BIND_DN='cn=admin,dc=min,dc=io' export MINIO_IDENTITY_LDAP_LOOKUP_BIND_PASSWORD=admin export MINIO_IDENTITY_LDAP_GROUP_SEARCH_BASE_DN='dc=minioad,dc=local;dc=somedomain,dc=com'
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 18.9K bytes - Viewed (0) -
docs/sts/wso2.md
MinIO server expects environment variable for OpenID configuration url as `MINIO_IDENTITY_OPENID_CONFIG_URL`, this environment variable takes a single entry. ``` export MINIO_IDENTITY_OPENID_CONFIG_URL=https://localhost:9443/oauth2/oidcdiscovery/.well-known/openid-configuration export MINIO_IDENTITY_OPENID_CLIENT_ID="843351d4-1080-11ea-aa20-271ecba3924a" minio server /mnt/data ```
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 8.7K bytes - Viewed (0) -
docs/sts/README.md
#### KeyCloak ``` export MINIO_ROOT_USER=minio export MINIO_ROOT_PASSWORD=minio123 export MINIO_IDENTITY_OPENID_CONFIG_URL=http://localhost:8080/auth/realms/demo/.well-known/openid-configuration export MINIO_IDENTITY_OPENID_CLIENT_ID="843351d4-1080-11ea-aa20-271ecba3924a" minio server /mnt/data ``` #### Casdoor ``` export MINIO_ROOT_USER=minio export MINIO_ROOT_PASSWORD=minio123
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 7.8K bytes - Viewed (0)