- Sort Score
- Result 10 results
- Languages All
Results 1 - 5 of 5 for destination (0.16 sec)
-
docs/sts/etcd.md
``` rm -rf /tmp/etcd-data.tmp && mkdir -p /tmp/etcd-data.tmp && \ podman rmi gcr.io/etcd-development/etcd:v3.3.9 || true && \ podman run \ -p 2379:2379 \ -p 2380:2380 \ --mount type=bind,source=/tmp/etcd-data.tmp,destination=/etcd-data \ --name etcd-gcr-v3.3.9 \ gcr.io/etcd-development/etcd:v3.3.9 \ /usr/local/bin/etcd \ --name s1 \ --data-dir /etcd-data \ --listen-client-urls http://0.0.0.0:2379 \
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 3.4K bytes - Viewed (0) -
docs/bucket/lifecycle/README.md
To transition objects in a bucket to a destination bucket on a different cluster, applications need to specify a transition tier defined on MinIO instead of storage class while setting up the ILM lifecycle rule.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Aug 26 07:33:25 GMT 2023 - 9K bytes - Viewed (1) -
docs/bucket/replication/README.md
To replicate objects in a bucket to a destination bucket on a target site either in the same cluster or a different cluster, start by enabling [versioning](https://min.io/docs/minio/linux/administration/object-management/object-versioning.html) for both source and destination buckets. Finally, the target site and the destination bucket need to be configured on the source MinIO server. ## Highlights
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Jan 24 23:46:33 GMT 2023 - 18.2K bytes - Viewed (0) -
docs/security/README.md
#### Key rotation S3 clients can change the client-provided key of an existing object. Therefore an S3 client must perform a S3 COPY operation where the copy source and destination are equal. Further the COPY request headers must contain the current and the new client key: - `X-Amz-Server-Side-Encryption-Customer-Key`: Base64 encoded new key.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Feb 12 00:51:25 GMT 2022 - 13.8K bytes - Viewed (0) -
docs/bucket/replication/DESIGN.md
take full advantage of two-way replication even before the two sites get fully synced. In the case of multi destination replication, the replication status shows `COMPLETED` only after the replication operation succeeds on each of the targets specified in the replication configuration. If multiple targets are configured to use active-active replication and multi destination replication, the administrator should ensure that the replication features enabled (such as replica metadata sync, delete...
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 14.7K bytes - Viewed (0)