...
Next create a folder in your user directory (or wherever you prefer) to hold the MinIO data: ~/data.
Create the environment variable file, setting leaving the server URL to localhostcommented out. You can save this file anywhere because you will point to it when starting up the server. I happened to put mine in the same directory as the MinIO data, so at, e.g. ~/data/.minio
| Code Block | ||
|---|---|---|
| ||
# MINIO_ROOT_USER and MINIO_ROOT_PASSWORD sets the root account for the MinIO server. # This user has unrestricted permissions to perform S3 and administrative API operations on any resource in the deployment. # Omit to use the default values 'minioadmin:minioadmin'. # MinIO recommends setting non-default values as a best practice, regardless of environment MINIO_ROOT_USER=myminioadmin MINIO_ROOT_PASSWORD=minio-secret-key-change-me # MINIO_VOLUMES sets the storage volume or path to use for the MinIO server. MINIO_VOLUMES="mnt/data" # MINIO_SERVER_URL sets the hostname of the local machine for use with the MinIO Server # MinIO assumes your network control plane can correctly resolve this hostname to the local machine MINIO#MINIO_SERVER_URL="http://localhostminio.example.net" |
Then point to your environment file when starting up (from within ~/data or whatever folder you have previously created for this):
...