bbs/clrghouz
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Update Minio Configuration

deon 2024-05-28 11:48:52 +00:00
parent 778c74e327
commit f1b3548ef2
1 changed files with 24 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
Minio-Configuration.md

@ -15,4 +15,27 @@ Some minio defaults that you can change if you want:
*NOTE:* *NOTE:*
* The settings we used on the [installation](Installation) page makes web UI port available from the host. So you should be able to go to `http://[HOST]:9001` and login with the admin username/password. (Where `HOST` is the hostname (or IP address) to your machine running hosting the clrghouz containers.) * The settings we used on the [installation](Installation) page makes web UI port available from the host. So you should be able to go to `http://[HOST]:9001` and login with the admin username/password. (Where `HOST` is the hostname (or IP address) to your machine running hosting the clrghouz containers.)
## Setup for clrghouz ## Setup for clrghouz
### Create a bucket to store files
Run this command:
```sh
> docker exec -it clrghouz-minio-1 mc mb /data/clrghouz
Bucket created successfully `/data/clrghouz`.
```
### Create a token to access minio
We need to create a token and secret for our `[MINIO_ACCESS_KEY]` and `[MINIO_SECRET_KEY]` as mentioned on [Installation](Installation).
The easiest way to do that is
1. Login to the minio web UI `http://[HOST]:9001` (where `[HOST]` is the hostname or IP address of the host running the clrghouz containers), using the details defined above. 2. Select `Access Keys` from the left
3. Select `+ Create access key` on the right
4. Press Create
5. Record the presented details in your `.env` file:
* Replace the Access Key `[MINIO_ACCESS_KEY]` with the created Access Key (its the value for AWS_ACCESS_KEY_ID)
* Replace the Secret Key `[MINIO_SECRET_KEY]` with the created Secret Key (its the value for AWS_SECRET_ACCESS_KEY)