add: local minio to docker compose

[ntheanh201]

More easier for new comers to work with local configured MinIO instead of the whole AWS S3 things

[matvp91]

Can we add this in a separate folder instead with more examples like minio?

I'd like to add this to the docs someday too. Know that I'm rewriting the documentation (pending PR here: #109) where I'd like to add these different options besides managed S3.

[ntheanh201]

Can we add this in a separate folder instead with more examples like minio?

I'd like to add this to the docs someday too. Know that I'm rewriting the documentation (pending PR here: #109) where I'd like to add these different options besides managed S3.

@matvp91 I updated the docker compose file

[matvp91]

Thank you, before I merge this, shall we be better off adding the actual env values to the minio docker-compose file instead as opposed to creating a new minio.env file?

Can we also remove the README.md changes? I'll take this up in the docs instead and keep the README rather compact.

[ntheanh201]

Thank you, before I merge this, shall we be better off adding the actual env values to the minio docker-compose file instead as opposed to creating a new minio.env file?

The purpose of adding new minio.env file is that if you choose to use another object storage and mix with another docker-compose file instead of MinIO, just give in the run command the other env file. Like --env-file s3.env. If you take a look at docker-compose.yml file, you can see the environment was defined like this:
- S3_ENDPOINT=${S3_ENDPOINT}
- S3_REGION=${S3_REGION}
- S3_ACCESS_KEY=${S3_ACCESS_KEY}
- S3_SECRET_KEY=${S3_SECRET_KEY}
- S3_BUCKET=${S3_BUCKET}

Do you have any idea? It's no good if we pass the default values of MinIO to these environment variables

[ntheanh201]

Can we also remove the README.md changes? I'll take this up in the docs instead and keep the README rather compact.

Reverted

[matvp91]

Perfect, lgtm! Thank you for contributing.