fuse: volumeServerAccess

FUSE-Mount.md

@@ -34,8 +34,8 @@ However, if the SeaweedFS cluster is started by Kubernetes or docker-compose and
 the volume servers only knows its own IP addresses inside the cluster, 
 `weed mount` is not able to access the volume servers from outside of the cluster.
 
-`weed mount -outsideContainerClusterMode` option can help here. It will proxy the requests to volume servers via filer.
-So only filer needs to be exposed.
+`weed mount -volumeServerAccess=[direct|publicUrl|filerProxy]` option can help here. You can choose to proxy the requests to volume servers via filer.
+So only filer needs to be exposed. Or you can choose to expose the public URLs of volume servers.
 
 #### Multiple mounts with multiple Filers of a SeaweedFS cluster
 

Production-Setup.md

@@ -176,7 +176,7 @@ Run
 
 * `-chunkCacheCountLimit` means how many entries cached in memory, default to 1000. With default `-chunkSizeLimitMB` set to 4, it may take up to 4x1000 MB memory. If all files are bigger than 4MB.
 * `-replication` is the replication level for each file. It overwrites replication settings on both filer and master.
-* `-outsideContainerClusterMode` is used if master, volume server, and filer are inside a cluster, but `weed mount` is outside of the cluster. With this option, only filer needs to be exposed to outside. All read write access to volume servers will be proxied by filer.
+* `-volumeServerAccess=[direct|publicUrl|filerProxy]` is used if master, volume server, and filer are inside a cluster, but `weed mount` is outside of the cluster. With this option set to `filerProxy`, only filer needs to be exposed to outside. All read write access to volume servers will be proxied by filer.
 
 ## Cluster Maintenance