jpike88 opened this issue 5 years ago · 1 comments
This is unavoidable since initialization is async, but as of v3.2.0, calling S3rver#configureBuckets before starting the HTTP server should be an acceptable workaround.
S3rver#configureBuckets