Polyglot Notebooks for multiple programming languages in Visual Studio Code.

Troubleshoot common user provisioning issues with SCIM and Just-in-Time provisioning

Learn how to manage organizations in a company.

An unbounded range (`..`).

!m.isStreaming) // Watch for store changes to focus input this.$watch('$store.gordon.isOpen', (isOpen) => { if (isOpe...

Run sandboxed AI coding agents using Docker Desktop and the docker sandbox CLI.

The mc version commands enable, disable, and retrieve the versioning status for an MinIO AIStor bucket. For more information about object versioning in MinIO, see Bucket Versioning. mc version includes the following subcommands: Subcommand Description enable Enable versioning on the specified bucket. info Return the versioning status for the specified bucket. suspend Disable versioning on the specified bucket.

The mc update command automatically updates the mc binary to the latest stable version. Running this command is equivalent to manually downloading the latest stable binary and using it to replace the existing mc installation on the host machine. Syntax Example The following command updates the mc binary on the local host:

Admin API v4 provides high-performance query endpoints for cluster introspection. These endpoints return information about cluster topology, nodes, drives, pools, and erasure sets using MessagePack binary encoding for efficient transfer. All endpoints require valid MinIO AIStor access credentials and the ServerInfoAdminAction authorization policy. Response format All query endpoints return binary MessagePack-encoded responses, not JSON. Use the madmin-go v4 client library to decode responses:

AIStor Server uses the built-in scanner to check objects for healing and to take any scheduled object actions. Such actions may include: calculate data usage on drives evaluate and apply configured lifecycle management or object retention rules perform bucket or site replication check objects for missing or corrupted data or parity shards and perform healing The scanner performs these functions at two levels: cluster and bucket. At the cluster level, the scanner splits all buckets into groups and scans one group of buckets at a time. The scanner starts with any new buckets added since the last scan, then randomizes the scanning of other buckets. The scanner completes checks on all bucket groups before starting over with a new set of scans.