Add. Optional MinIO Service for File Storage #40
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces an optional MinIO service to the Docker Compose setup for the Medispeak backend. MinIO provides an alternative to AWS S3 for file storage, while maintaining compatibility with the S3 API. This update includes the necessary environment variables and configuration changes to enable seamless switching between MinIO and AWS S3.
Changes:
docker-compose.yml
under theminio
profile..env
file.storage.yml
configuration to support MinIO as an S3-compatible storage option.STORAGE_SERVICE
environment variable to toggle between storage providers (minio
,amazon
,local
).Usage:
To enable the MinIO service, run the following command:
Ensure the relevant environment variables are set for MinIO in the
.env
file.Notes:
Issue Reference:
This PR addresses Issue #39 raised in the Medispeak backend repository.