You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on migrating from Docker Compose to Kubernetes, and I'm facing a problem with communication between museum and minio. My museum.yaml has the S3 endpoint configured with my domain (for correct minio selection in web and mobile apps). The issue is that museum is also attempting to use this external endpoint. Is there a way to configure museum to use a different domain for minio access compared to the web service?
The text was updated successfully, but these errors were encountered:
I'm working on migrating from Docker Compose to Kubernetes, and I'm facing a problem with communication between museum and minio. My museum.yaml has the S3 endpoint configured with my domain (for correct minio selection in web and mobile apps). The issue is that museum is also attempting to use this external endpoint. Is there a way to configure museum to use a different domain for minio access compared to the web service?
The text was updated successfully, but these errors were encountered: