Docker samples for React.

Learn about profiles

The resolvedOptions() method of Intl.Segmenter instances returns a new object with properties reflecting the options computed during initialization of this Segmenter object.

This procedure downloads and installs the AIStor Server onto baremetal hosts running Red Hat Enterprise Linux Review the Hardware and System Requirements to ensure your target infrastructure meets our guidance. You can also open a SUBNET to request an architecture review or assistance during deployment. MinIO strongly recommends using only RHEL releases in the Full Support lifecycle with Long-Term Support (LTS) Kernels in the 6.6 or later release series, such as RHEL 10.

The mc admin cluster bucket export command exports bucket metadata for use with the (mc admin cluster bucket import) command. You can use this command to manually back up the metadata for the specified AIStor bucket. The command always saves the output as cluster-metadata.zip. If you specify only the deployment as the target, this command backs up all bucket metadata on the target deployment.

AIStor supports publishing bucket notification events to NSQ service endpoint. Prerequisites The AIStor mc Command Line Tool This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions. Add an NSQ endpoint to an AIStor Server The following procedure adds a new NSQ service endpoint for supporting bucket notifications in an AIStor Server.

This page documents the steps necessary to remove a peer site from existing Site Replication configuration. Remove the Peer Site using AIStor Console In a browser, access the Console for one of the existing replicated sites.

Install on Red Hat Enterprise Linux Deploy AIStor onto RHEL 10+

This procedure provides guidance for enabling Server-Side Encryption (SSE) using AIStor Key Manager as the Key Management Service (KMS). Enabling SSE on an AIStor deployment automatically encrypts the backend data for that deployment using the default encryption key selected during the setup process. AIStor requires access to the Key Manager to decrypt the backend and start normally. You can neither disable nor reset encryption of the backend.

Overview AIStor supports keeping multiple “versions” of an object in a single bucket. When enabled, versioning allows AIStor to keep multiple iterations of the same object. Write operations which would normally overwrite an existing object instead result in the creation of a new version of the object. AIStor versioning protects from unintended overwrites and deletions while providing support for “undoing” a write operation. Bucket versioning is a prerequisite for configuring object locking and retention rules.