mirror of
https://github.com/minio/docs.git
synced 2025-07-30 07:03:26 +03:00
Improve documentation on MINIO_DOMAIN (#1131)
# Summary As per a recent customer issue, our guidance on `MINIO_DOMAIN` and path/virtual bucket lookups needs some attention. There are two main areas to address: 1. We need to guide users to avoid namespace collision within the `MINIO_DOMAIN` , as this causes bucket lookup issues with certain MinIO services/features 2. We need to generally improve docs on setting `MINIO_DOMAIN` correctly There is also a side objective from Engineering to ensure we have a simple admonition to direct users to test wherever possible changes to config settings before applying to production. --------- Co-authored-by: Daryl White <53910321+djwfyi@users.noreply.github.com>
This commit is contained in:
@ -107,4 +107,13 @@ If you define both an environment variable and the similar configuration setting
|
||||
|
||||
Some settings have only an environment variable or a configuration setting, but not both.
|
||||
|
||||
.. end-minio-settings-defined
|
||||
.. end-minio-settings-defined
|
||||
|
||||
.. start-minio-settings-test-before-prod
|
||||
|
||||
.. important::
|
||||
|
||||
Each configuration setting controls fundamental MinIO behavior and functionality.
|
||||
MinIO **strongly recommends** testing configuration changes in a lower environment, such as DEV or QA, before applying to production.
|
||||
|
||||
.. end-minio-settings-test-before-prod
|
Reference in New Issue
Block a user