* terminal: terminal (femenine, as in "la terminal")
* terminals: terminales (plural femenine, as in "las terminales")
* lifespan: lifespan (do not translate to "vida útil" or "tiempo de vida")
* unload: quitar de memoria (do not translate to "descargar")
* mount (noun): mount (do not translate to "montura")
* mount (verb): montar

* feature: funcionalidade
* guides: tutoriais
* I/O (as in "input and output"): I/O (do not translate to "E/S")
* JSON Schema: JSON Schema
* library: biblioteca
* lifespan: lifespan (do not translate to "vida útil")
* list (as in Python list): list
* Machine Learning: Aprendizado de Máquina
* media type: media type (do not translate to "tipo de mídia")

1/xl.meta XL2 Æ b ¨Versions‘‚¤Type ¥V2ObjÞ ¢IDÄ ¤DDirÄ ÔLã°ê8EÒŸˆ”Ù Sé6¦EcAlgo £EcM £EcN §EcBSizeÒ §EcIndex ¦EcDistš ¨CSumAlgo ¨PartNums‘ ©PartETags‘ ©PartSizes‘Ò 'ªPartASizes‘Ò '¤SizeÒ 'Â¥MTimeÓ ¿W '’žÉ§MetaSys ¼X-Minio-Internal-actual-sizeÄ 141250§MetaUsr‚¤etagÙ"51fe09d68bacc8c5a68a-1¬content-type¸application/octet-streamÎöa‰ 10/xl.meta XL2 Æ b ¨Versions‘‚¤Type ¥V2ObjÞ ¢IDÄ ¤DDirÄ ÔLã°ê8EÒŸˆ”Ù Sé6¦EcAlgo £EcM £EcN §EcBSizeÒ §EcIndex ¦EcDistš ¨CSumAlgo ¨PartNums‘ ©PartETags‘ ©PartSizes‘Ò 'ªPartASizes‘Ò...

Dessa forma, a sub-aplicação saberá usar esse prefixo de path para a interface de documentação.

E a sub-aplicação também poderia ter suas próprias sub-aplicações montadas e tudo funcionaria corretamente, porque o FastAPI lida com todos esses `root_path`s automaticamente.

		vID, err := uuid.Parse(fi.TierFreeVersionID())
		if err != nil {
			panic(fmt.Errorf("Invalid Tier Object delete marker versionId %s %v", fi.TierFreeVersionID(), err))
		}
		freeEntry := xlMetaV2Version{Type: DeleteType, WrittenByVersion: globalVersionUnix}
		freeEntry.DeleteMarker = &xlMetaV2DeleteMarker{
			VersionID: vID,
			ModTime:   j.ModTime, // fi.ModTime may be empty

## Authentication Flow

A client can request temp. S3 credentials via the STS API. It can authenticate via a client certificate and obtain a access/secret key pair as well as a session token. These credentials are associated to an S3 policy at the MinIO server.

- All sites must be using the **same** external IDP(s) if any.
- For [SSE-S3 or SSE-KMS encryption via KMS](https://docs.min.io/community/minio-object-store/operations/server-side-encryption.html "MinIO KMS Guide"), all sites **must**  have access to a central KMS deployment. This can be achieved via a central KES server or multiple KES servers (say one per site) connected via a central KMS (Vault) server.

## Configuring Site Replication

MinIO now supports starting the server arguments and configuration via a YAML configuration file. This YAML configuration describes everything that can be configured in a MinIO setup, such as '--address', '--console-address' and command line arguments for the MinIO server.

export MINIO_STORAGE_CLASS_STANDARD=EC:3
export MINIO_STORAGE_CLASS_RRS=EC:2
```

Storage class can also be set via `mc admin config` get/set commands to update the configuration. Refer [storage class](https://github.com/minio/minio/tree/master/docs/config#storage-class) for
more details.

#### Note

        } else if (androidStudioHome.isPresent) {
            return "-Dstudio.home=${androidStudioHome.get()}"
        }
        throw IllegalArgumentException("Android Studio home must be provided via the 'studioHome' system property, or auto downloading must be enabled via `autoDownloadAndroidStudio=true` gradle property, system property, or environment variable")
    }