Skip to content
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

Properly expose Minio server #8

Open
2 tasks
holtgrewe opened this issue Jun 20, 2023 · 0 comments
Open
2 tasks

Properly expose Minio server #8

holtgrewe opened this issue Jun 20, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@holtgrewe
Copy link
Contributor

Is your feature request related to a problem? Please describe.
The Minio server is not properly exposed currently.

Describe the solution you'd like
Add configuration that exposes the server through port 9000 on the host via traefik. Effectively, the default configuration is then:

  • <catch-all hostnames>:80 -- HTTP, redirect to HTTPS
  • <catch-all hostnames>:443 -- HTTPS, server varfish-server
  • <catch-all hostnames>:9000 -- HTTPS, server minio

Users may want to configure different hostname and expose minio via HTTPS on their hostname. This will require more special configuration, in particular when custom certificates are used. We should provide some example configuration as a docker-compose.override.yml fragment.

  • default configuration
  • override YAML fragment for different hostnames

Describe alternatives you've considered
N/A

Additional context
N/A

@holtgrewe holtgrewe added the enhancement New feature or request label Jan 24, 2024
@holtgrewe holtgrewe moved this to To triage in Release Planning Jan 24, 2024
@holtgrewe holtgrewe moved this from To triage to Backlog in Release Planning Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

1 participant