Cheol,
Message in the service console does not mean that service was connected properly. It only shows that service is configured.
We had some issues when minio was not available, where errors occurred only when trying to access some stored filedocuments (in our case xml file with metadata for SAML module).
During startup (when minio was not available too), no errors were reported in console log.
What kind of error do you get when "it doesn’t work.”?
Edit: Please add this parameter too: 'com.mendix.core.StorageService=com.mendix.storage.s3'
Hi Edwin,
Thank you for your information and help.
There is no error messages in service console.
I changed the log level to trace. There is no messages.
When I adding a file, it stored in windows file path.
My intention is storing it Mino.
The minio is working properly with mendix app on docker environment.
I tried to integrate minio and windows service console.
The setting parameters' name are different between dockerfile and win service console.
I wonder if the com.mendix.storage.s3.* are the right parameter name.
Best Regards
Charlie
Hi Edwin,
Thank you for your information and help.
There is no error messages in service console.
I changed the log level to trace. There is no messages.
When I adding a file, it stored in windows file path.
My intention is storing it Mino.
The minio is working properly with mendix app on docker environment.
I tried to integrate minio and windows service console.
The setting parameters' name are different between dockerfile and win service console.
I wonder if the com.mendix.storage.s3.* are the right parameter name.
Best Regards
Charlie
Hi Edwin van Elk,
Thanks to your help and support I could make it.
I added customer settings as attached.
Huge thanks again for your help.
com.mendix.storage.s3.EndPoint http:192.168.40.151:9100
com.mendix.storage.s3.BucketName mx8103a
com.mendix.storage.s3.AccessKeyId minio
com.mendix.storage.s3.SecretAccessKey minio123
com.mendix.core.StorageService com.mendix.storage.s3
Best Regards,
Charlie