Skip to content

Self host museum and minio problem #5689

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
WorldOfWheat opened this issue Apr 22, 2025 · 0 comments
Open

Self host museum and minio problem #5689

WorldOfWheat opened this issue Apr 22, 2025 · 0 comments

Comments

@WorldOfWheat
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant