chore: add Milvus TLS env examples

Author: laipz8200

docker/README.md

@@ -66,6 +66,9 @@ For users migrating from the `docker-legacy` setup:
 - `.env` contains local startup values copied from `.env.example` and any local changes.
 - `envs/*.env.example` files contain optional advanced configuration grouped by theme.
 
+Keep the root `.env.example` limited to variables required to start the default Docker Compose deployment.
+Do not add optional, advanced, provider-specific, or service-specific variables there; place them in the appropriate `envs/*.env.example` file instead.
+
 Docker Compose reads `envs/*.env` files when present, then reads `.env` last so values in `.env` take precedence.
 
 #### Key Modules and Customization
@@ -128,7 +131,8 @@ The root `.env.example` file contains the essential startup settings. Optional a
 
 ### Environment Variables Synchronization
 
-When upgrading Dify or pulling the latest changes, new environment variables may be introduced in `.env.example` or the optional files under `envs/`.
+When upgrading Dify or pulling the latest changes, new environment variables may be introduced in `.env.example` only when they are required for startup,
+or in the optional files under `envs/` for advanced, provider-specific, and service-specific settings.
 
 If you use the default workflow, review `.env.example` and keep your `.env` aligned with essential startup values.
 

docker/envs/vectorstores/milvus.env.example

@@ -11,3 +11,6 @@ ETCD_AUTO_COMPACTION_RETENTION=1000
 ETCD_QUOTA_BACKEND_BYTES=4294967296
 ETCD_SNAPSHOT_COUNT=50000
 MILVUS_AUTHORIZATION_ENABLED=true
+MILVUS_SECURE=false
+MILVUS_SERVER_PEM_PATH=
+MILVUS_SERVER_NAME=