From e5e522fc6167e2e870562fd08e8d9f39bacad3ad Mon Sep 17 00:00:00 2001 From: Harshavardhana Date: Thu, 28 Jun 2018 16:02:02 -0700 Subject: [PATCH] docs: fix all Chinese doc links for the new docs site (#6097) Additionally fix typos, default to US locale words --- Makefile | 8 +++++--- buildscripts/checkdeps.sh | 2 +- cmd/admin-heal-ops.go | 6 +++--- cmd/bucket-handlers-listobjects.go | 4 ++-- cmd/disk-cache.go | 2 +- cmd/fs-v1-multipart.go | 2 +- cmd/fs-v1.go | 2 +- cmd/generic-handlers.go | 2 +- cmd/namespace-lock_test.go | 2 +- cmd/posix_test.go | 2 +- cmd/posix_windows_test.go | 2 +- cmd/server_test.go | 2 +- cmd/update-main.go | 2 +- cmd/xl-sets.go | 2 +- cmd/xl-v1-metadata.go | 2 +- cmd/xl-v1-multipart.go | 4 ++-- cmd/xl-v1-object.go | 2 +- dockerscripts/healthcheck.sh | 2 +- docs/bucket/notifications/README.md | 2 +- docs/config/README.md | 18 +++++++++--------- docs/erasure/README.md | 2 +- docs/erasure/storage-class/README.md | 4 ++-- docs/minio-limits.md | 8 ++++---- docs/orchestration/README.md | 8 ++++---- docs/zh_CN/bucket/notifications/README.md | 6 +++--- docs/zh_CN/config/README.md | 18 +++++++++--------- docs/zh_CN/distributed/README.md | 16 ++++++++-------- docs/zh_CN/docker/README.md | 10 +++++----- docs/zh_CN/erasure/README.md | 2 +- docs/zh_CN/gateway/azure.md | 8 ++++---- docs/zh_CN/gateway/gcs.md | 8 ++++---- docs/zh_CN/minio-limits.md | 8 ++++---- docs/zh_CN/multi-tenancy/README.md | 2 +- docs/zh_CN/orchestration/README.md | 8 ++++---- docs/zh_CN/orchestration/dcos/README.md | 2 +- .../orchestration/docker-compose/README.md | 8 ++++---- .../zh_CN/orchestration/docker-swarm/README.md | 10 +++++----- .../orchestration/kubernetes-yaml/README.md | 2 +- docs/zh_CN/orchestration/kubernetes/README.md | 4 ++-- docs/zh_CN/shared-backend/README.md | 12 ++++++------ docs/zh_CN/tls/README.md | 6 +++--- pkg/madmin/config-commands.go | 2 +- 42 files changed, 113 insertions(+), 111 deletions(-) diff --git a/Makefile b/Makefile index 259309ea1..a29b7b2b5 100644 --- a/Makefile +++ b/Makefile @@ -50,9 +50,11 @@ deadcode: @${GOPATH}/bin/deadcode -test $(shell go list ./...) || true spelling: - @${GOPATH}/bin/misspell -error `find cmd/` - @${GOPATH}/bin/misspell -error `find pkg/` - @${GOPATH}/bin/misspell -error `find docs/` + @${GOPATH}/bin/misspell -locale US -error `find cmd/` + @${GOPATH}/bin/misspell -locale US -error `find pkg/` + @${GOPATH}/bin/misspell -locale US -error `find docs/` + @${GOPATH}/bin/misspell -locale US -error `find buildscripts/` + @${GOPATH}/bin/misspell -locale US -error `find dockerscripts/` # Builds minio, runs the verifiers then runs the tests. check: test diff --git a/buildscripts/checkdeps.sh b/buildscripts/checkdeps.sh index ec8cb7130..d61657e52 100644 --- a/buildscripts/checkdeps.sh +++ b/buildscripts/checkdeps.sh @@ -34,7 +34,7 @@ _init() { ## FIXME: ## In OSX, 'readlink -f' option does not exist, hence -## we have our own readlink -f behaviour here. +## we have our own readlink -f behavior here. ## Once OSX has the option, below function is good enough. ## ## readlink() { diff --git a/cmd/admin-heal-ops.go b/cmd/admin-heal-ops.go index 5a8c94f2b..b39b2ecf1 100644 --- a/cmd/admin-heal-ops.go +++ b/cmd/admin-heal-ops.go @@ -57,7 +57,7 @@ const ( var ( errHealIdleTimeout = fmt.Errorf("healing results were not consumed for too long") errHealPushStopNDiscard = fmt.Errorf("heal push stopped due to heal stop signal") - errHealStopSignalled = fmt.Errorf("heal stop signalled") + errHealStopSignalled = fmt.Errorf("heal stop signaled") errFnHealFromAPIErr = func(err error) error { errCode := toAPIErrorCode(err) @@ -301,7 +301,7 @@ type healSequence struct { // current accumulated status of the heal sequence currentStatus healSequenceStatus - // channel signalled by background routine when traversal has + // channel signaled by background routine when traversal has // completed traverseAndHealDoneCh chan error @@ -441,7 +441,7 @@ func (h *healSequence) pushHealResultItem(r madmin.HealResultItem) error { h.currentStatus.updateLock.Unlock() // This is a "safe" point for the heal sequence to quit if - // signalled externally. + // signaled externally. if h.isQuitting() { return errHealStopSignalled } diff --git a/cmd/bucket-handlers-listobjects.go b/cmd/bucket-handlers-listobjects.go index da91fd238..b0fab7083 100644 --- a/cmd/bucket-handlers-listobjects.go +++ b/cmd/bucket-handlers-listobjects.go @@ -100,7 +100,7 @@ func (api objectAPIHandlers) ListObjectsV2Handler(w http.ResponseWriter, r *http } // Inititate a list objects operation based on the input params. // On success would return back ListObjectsInfo object to be - // marshalled into S3 compatible XML header. + // marshaled into S3 compatible XML header. listObjectsV2Info, err := listObjectsV2(ctx, bucket, prefix, marker, delimiter, maxKeys, fetchOwner, startAfter) if err != nil { writeErrorResponse(w, toAPIErrorCode(err), r.URL) @@ -166,7 +166,7 @@ func (api objectAPIHandlers) ListObjectsV1Handler(w http.ResponseWriter, r *http } // Inititate a list objects operation based on the input params. // On success would return back ListObjectsInfo object to be - // marshalled into S3 compatible XML header. + // marshaled into S3 compatible XML header. listObjectsInfo, err := listObjects(ctx, bucket, prefix, marker, delimiter, maxKeys) if err != nil { writeErrorResponse(w, toAPIErrorCode(err), r.URL) diff --git a/cmd/disk-cache.go b/cmd/disk-cache.go index 6a67ebac7..a9fe5b851 100644 --- a/cmd/disk-cache.go +++ b/cmd/disk-cache.go @@ -238,7 +238,7 @@ func (c cacheObjects) GetObject(ctx context.Context, bucket, object string, star pipeWriter.CloseWithError(err) return } - pipeWriter.Close() // Close writer explicitly signalling we wrote all data. + pipeWriter.Close() // Close writer explicitly signaling we wrote all data. }() err = dcache.Put(ctx, bucket, object, hashReader, c.getMetadata(objInfo)) if err != nil { diff --git a/cmd/fs-v1-multipart.go b/cmd/fs-v1-multipart.go index 7cda9f2a9..6459a84c6 100644 --- a/cmd/fs-v1-multipart.go +++ b/cmd/fs-v1-multipart.go @@ -264,7 +264,7 @@ func (fs *FSObjects) CopyObjectPart(ctx context.Context, srcBucket, srcObject, d } return } - // Close writer explicitly signalling we wrote all data. + // Close writer explicitly signaling we wrote all data. if gerr := srcInfo.Writer.Close(); gerr != nil { logger.LogIf(ctx, gerr) return diff --git a/cmd/fs-v1.go b/cmd/fs-v1.go index 872df1880..a6b98d5a7 100644 --- a/cmd/fs-v1.go +++ b/cmd/fs-v1.go @@ -505,7 +505,7 @@ func (fs *FSObjects) CopyObject(ctx context.Context, srcBucket, srcObject, dstBu } return } - // Close writer explicitly signalling we wrote all data. + // Close writer explicitly signaling we wrote all data. if gerr := srcInfo.Writer.Close(); gerr != nil { logger.LogIf(ctx, gerr) return diff --git a/cmd/generic-handlers.go b/cmd/generic-handlers.go index 9f58c27e2..e6495676b 100644 --- a/cmd/generic-handlers.go +++ b/cmd/generic-handlers.go @@ -688,7 +688,7 @@ func setBucketForwardingHandler(h http.Handler) http.Handler { // rate.Limiter token bucket configured with maxOpenFileLimit and // burst set to 1. The request will idle for up to 1*time.Second. // If the limiter detects the deadline will be exceeded, the request is -// cancelled immediately. +// canceled immediately. func setRateLimitHandler(h http.Handler) http.Handler { _, maxLimit, err := sys.GetMaxOpenFileLimit() logger.FatalIf(err, "Unable to get maximum open file limit", context.Background()) diff --git a/cmd/namespace-lock_test.go b/cmd/namespace-lock_test.go index 1e868370d..54151cf44 100644 --- a/cmd/namespace-lock_test.go +++ b/cmd/namespace-lock_test.go @@ -226,7 +226,7 @@ func TestNamespaceForceUnlockTest(t *testing.T) { select { case <-ch: - // Signalled so all is fine. + // Signaled so all is fine. break case <-time.After(100 * time.Millisecond): diff --git a/cmd/posix_test.go b/cmd/posix_test.go index f3f208cef..bc7d95ae7 100644 --- a/cmd/posix_test.go +++ b/cmd/posix_test.go @@ -470,7 +470,7 @@ func TestPosixMakeVol(t *testing.T) { } } -// TestPosixDeleteVol - Validates the expected behaviour of posix.DeleteVol for various cases. +// TestPosixDeleteVol - Validates the expected behavior of posix.DeleteVol for various cases. func TestPosixDeleteVol(t *testing.T) { // create posix test setup posixStorage, path, err := newPosixTestSetup() diff --git a/cmd/posix_windows_test.go b/cmd/posix_windows_test.go index e34295cf9..91ca8ab4d 100644 --- a/cmd/posix_windows_test.go +++ b/cmd/posix_windows_test.go @@ -69,7 +69,7 @@ func TestUNCPaths(t *testing.T) { } } -// Test to validate posix behaviour on windows when a non-final path component is a file. +// Test to validate posix behavior on windows when a non-final path component is a file. func TestUNCPathENOTDIR(t *testing.T) { var err error // Instantiate posix object to manage a disk diff --git a/cmd/server_test.go b/cmd/server_test.go index 9ca777325..f6254528f 100644 --- a/cmd/server_test.go +++ b/cmd/server_test.go @@ -2420,7 +2420,7 @@ func (s *TestSuiteCommon) TestBucketMultipartList(c *check) { // unmarshalling works from a client perspective, specifically // while unmarshalling time.Time type for 'Initiated' field. // time.Time does not honor xml marshaler, it means that we need - // to encode/format it before giving it to xml marshalling. + // to encode/format it before giving it to xml marshaling. // This below check adds client side verification to see if its // truly parseable. diff --git a/cmd/update-main.go b/cmd/update-main.go index 0a969386d..5cc1f0a49 100644 --- a/cmd/update-main.go +++ b/cmd/update-main.go @@ -458,7 +458,7 @@ func getUpdateInfo(timeout time.Duration, mode string) (updateMsg string, sha256 func doUpdate(sha256Hex string, latestReleaseTime time.Time, ok bool) (successMsg string, err error) { if !ok { - successMsg = greenColorSprintf("Minio update to version RELEASE.%s cancelled.", + successMsg = greenColorSprintf("Minio update to version RELEASE.%s canceled.", latestReleaseTime.Format(minioReleaseTagTimeLayout)) return successMsg, nil } diff --git a/cmd/xl-sets.go b/cmd/xl-sets.go index e2916cfe9..5d9170438 100644 --- a/cmd/xl-sets.go +++ b/cmd/xl-sets.go @@ -614,7 +614,7 @@ func (s *xlSets) CopyObject(ctx context.Context, srcBucket, srcObject, destBucke } return } - // Close writer explicitly signalling we wrote all data. + // Close writer explicitly signaling we wrote all data. if gerr := srcInfo.Writer.Close(); gerr != nil { logger.LogIf(ctx, gerr) return diff --git a/cmd/xl-v1-metadata.go b/cmd/xl-v1-metadata.go index 42fa5b92e..4c9319a4e 100644 --- a/cmd/xl-v1-metadata.go +++ b/cmd/xl-v1-metadata.go @@ -463,7 +463,7 @@ func writeXLMetadata(ctx context.Context, disk StorageAPI, bucket, prefix string logger.LogIf(ctx, err) return err } - // Persist marshalled data. + // Persist marshaled data. err = disk.AppendFile(bucket, jsonFile, metadataBytes) logger.LogIf(ctx, err) return err diff --git a/cmd/xl-v1-multipart.go b/cmd/xl-v1-multipart.go index f17d33902..9a9e68801 100644 --- a/cmd/xl-v1-multipart.go +++ b/cmd/xl-v1-multipart.go @@ -277,7 +277,7 @@ func (xl xlObjects) CopyObjectPart(ctx context.Context, srcBucket, srcObject, ds } return } - // Close writer explicitly signalling we wrote all data. + // Close writer explicitly signaling we wrote all data. if gerr := srcInfo.Writer.Close(); gerr != nil { logger.LogIf(ctx, gerr) return @@ -482,7 +482,7 @@ func (xl xlObjects) PutObjectPart(ctx context.Context, bucket, object, uploadID // to indicate where the listing should begin from. // // Implements S3 compatible ListObjectParts API. The resulting -// ListPartsInfo structure is marshalled directly into XML and +// ListPartsInfo structure is marshaled directly into XML and // replied back to the client. func (xl xlObjects) ListObjectParts(ctx context.Context, bucket, object, uploadID string, partNumberMarker, maxParts int) (result ListPartsInfo, e error) { if err := checkListPartsArgs(ctx, bucket, object, xl); err != nil { diff --git a/cmd/xl-v1-object.go b/cmd/xl-v1-object.go index ce23e64cc..f25382bb1 100644 --- a/cmd/xl-v1-object.go +++ b/cmd/xl-v1-object.go @@ -142,7 +142,7 @@ func (xl xlObjects) CopyObject(ctx context.Context, srcBucket, srcObject, dstBuc pipeWriter.CloseWithError(toObjectErr(gerr, srcBucket, srcObject)) return } - pipeWriter.Close() // Close writer explicitly signalling we wrote all data. + pipeWriter.Close() // Close writer explicitly signaling we wrote all data. }() hashReader, err := hash.NewReader(pipeReader, length, "", "") diff --git a/dockerscripts/healthcheck.sh b/dockerscripts/healthcheck.sh index 28b7d39cb..82b65648b 100755 --- a/dockerscripts/healthcheck.sh +++ b/dockerscripts/healthcheck.sh @@ -48,7 +48,7 @@ healthcheck_main () { http_response=$(curl -s -k -o /dev/null -w "%{http_code}" ${scheme}${address}${resource}) fi - # If http_repsonse is 200 - server is up. + # If http_response is 200 - server is up. [ "$http_response" = "200" ] fi } diff --git a/docs/bucket/notifications/README.md b/docs/bucket/notifications/README.md index c89cafeca..58461baac 100644 --- a/docs/bucket/notifications/README.md +++ b/docs/bucket/notifications/README.md @@ -20,7 +20,7 @@ Bucket events can be published to the following targets: ## Prerequisites -* Install and configure Minio Server from [here](http://docs.minio.io/docs/minio-quickstart-guide). +* Install and configure Minio Server from [here](https://docs.minio.io/docs/minio-quickstart-guide). * Install and configure Minio Client from [here](https://docs.minio.io/docs/minio-client-quickstart-guide). diff --git a/docs/config/README.md b/docs/config/README.md index 1fb910f3c..3e4870644 100644 --- a/docs/config/README.md +++ b/docs/config/README.md @@ -10,7 +10,7 @@ minio server --config-dir /etc/minio /data ``` ### Certificate Directory -TLS certificates are stored under ``${HOME}/.minio/certs`` directory. You need to place certificates here to enable `HTTPS` based access. Read more about [How to secure access to Minio server with TLS](http://docs.minio.io/docs/how-to-secure-access-to-minio-server-with-tls). +TLS certificates are stored under ``${HOME}/.minio/certs`` directory. You need to place certificates here to enable `HTTPS` based access. Read more about [How to secure access to Minio server with TLS](https://docs.minio.io/docs/how-to-secure-access-to-minio-server-with-tls). Following is the directory structure for Minio server with TLS certificates. @@ -115,15 +115,15 @@ By default, parity for objects with standard storage class is set to `N/2`, and |Field|Type|Description| |:---|:---|:---| |``notify``| |Notify enables bucket notification events for lambda computing via the following targets.| -|``notify.amqp``| |[Configure to publish Minio events via AMQP target.](http://docs.minio.io/docs/minio-bucket-notification-guide#AMQP)| -|``notify.nats``| |[Configure to publish Minio events via NATS target.](http://docs.minio.io/docs/minio-bucket-notification-guide#NATS)| -|``notify.elasticsearch``| |[Configure to publish Minio events via Elasticsearch target.](http://docs.minio.io/docs/minio-bucket-notification-guide#Elasticsearch)| -|``notify.redis``| |[Configure to publish Minio events via Redis target.](http://docs.minio.io/docs/minio-bucket-notification-guide#Redis)| -|``notify.postgresql``| |[Configure to publish Minio events via PostgreSQL target.](http://docs.minio.io/docs/minio-bucket-notification-guide#PostgreSQL)| -|``notify.kafka``| |[Configure to publish Minio events via Apache Kafka target.](http://docs.minio.io/docs/minio-bucket-notification-guide#apache-kafka)| -|``notify.webhook``| |[Configure to publish Minio events via Webhooks target.](http://docs.minio.io/docs/minio-bucket-notification-guide#webhooks)| +|``notify.amqp``| |[Configure to publish Minio events via AMQP target.](https://docs.minio.io/docs/minio-bucket-notification-guide#AMQP)| +|``notify.nats``| |[Configure to publish Minio events via NATS target.](https://docs.minio.io/docs/minio-bucket-notification-guide#NATS)| +|``notify.elasticsearch``| |[Configure to publish Minio events via Elasticsearch target.](https://docs.minio.io/docs/minio-bucket-notification-guide#Elasticsearch)| +|``notify.redis``| |[Configure to publish Minio events via Redis target.](https://docs.minio.io/docs/minio-bucket-notification-guide#Redis)| +|``notify.postgresql``| |[Configure to publish Minio events via PostgreSQL target.](https://docs.minio.io/docs/minio-bucket-notification-guide#PostgreSQL)| +|``notify.kafka``| |[Configure to publish Minio events via Apache Kafka target.](https://docs.minio.io/docs/minio-bucket-notification-guide#apache-kafka)| +|``notify.webhook``| |[Configure to publish Minio events via Webhooks target.](https://docs.minio.io/docs/minio-bucket-notification-guide#webhooks)| |``notify.mysql``| |[Configure to publish Minio events via MySql target.](https://docs.minio.io/docs/minio-bucket-notification-guide#MySQL)| -|``notify.mqtt``| |[Configure to publish Minio events via MQTT target.](http://docs.minio.io/docs/minio-bucket-notification-guide#MQTT)| +|``notify.mqtt``| |[Configure to publish Minio events via MQTT target.](https://docs.minio.io/docs/minio-bucket-notification-guide#MQTT)| ## Explore Further * [Minio Quickstart Guide](https://docs.minio.io/docs/minio-quickstart-guide) diff --git a/docs/erasure/README.md b/docs/erasure/README.md index caa0c462b..31207eaec 100644 --- a/docs/erasure/README.md +++ b/docs/erasure/README.md @@ -18,7 +18,7 @@ Erasure code protects data from multiple drives failure, unlike RAID or replicat ## What is Bit Rot protection? -Bit Rot, also known as data rot or silent data corruption is a data loss issue faced by disk drives today. Data on the drive may silently get corrupted without signalling an error has occurred, making bit rot more dangerous than a permanent hard drive failure. +Bit Rot, also known as data rot or silent data corruption is a data loss issue faced by disk drives today. Data on the drive may silently get corrupted without signaling an error has occurred, making bit rot more dangerous than a permanent hard drive failure. Minio's erasure coded backend uses high speed [HighwayHash](https://blog.minio.io/highwayhash-fast-hashing-at-over-10-gb-s-per-core-in-golang-fee938b5218a) checksums to protect against Bit Rot. diff --git a/docs/erasure/storage-class/README.md b/docs/erasure/storage-class/README.md index d8eedf642..4f9f33581 100644 --- a/docs/erasure/storage-class/README.md +++ b/docs/erasure/storage-class/README.md @@ -11,8 +11,8 @@ saving the object in specific number of data and parity disks. ## Storage usage -The selection of varying data and parity drives has a direct impact on the drive space usage. With storage class, you can optimise for high -redundancy or better drive space utilisation. +The selection of varying data and parity drives has a direct impact on the drive space usage. With storage class, you can optimize for high +redundancy or better drive space utilization. To get an idea of how various combinations of data and parity drives affect the storage usage, let’s take an example of a 100 MiB file stored on 16 drive Minio deployment. If you use eight data and eight parity drives, the file space usage will be approximately twice, i.e. 100 MiB diff --git a/docs/minio-limits.md b/docs/minio-limits.md index 69c6c57d2..afdc4e2fd 100644 --- a/docs/minio-limits.md +++ b/docs/minio-limits.md @@ -36,19 +36,19 @@ We found the following APIs to be redundant or less useful outside of AWS S3. If #### List of Amazon S3 Bucket API's not supported on Minio -- BucketACL (Use [bucket policies](http://docs.minio.io/docs/minio-client-complete-guide#policy) instead) +- BucketACL (Use [bucket policies](https://docs.minio.io/docs/minio-client-complete-guide#policy) instead) - BucketCORS (CORS enabled by default on all buckets for all HTTP verbs) - BucketLifecycle (Not required for Minio erasure coded backend) -- BucketReplication (Use [`mc mirror`](http://docs.minio.io/docs/minio-client-complete-guide#mirror) instead) +- BucketReplication (Use [`mc mirror`](https://docs.minio.io/docs/minio-client-complete-guide#mirror) instead) - BucketVersions, BucketVersioning (Use [`s3git`](https://github.com/s3git/s3git)) - BucketWebsite (Use [`caddy`](https://github.com/mholt/caddy) or [`nginx`](https://www.nginx.com/resources/wiki/)) -- BucketAnalytics, BucketMetrics, BucketLogging (Use [bucket notification](http://docs.minio.io/docs/minio-client-complete-guide#events) APIs) +- BucketAnalytics, BucketMetrics, BucketLogging (Use [bucket notification](https://docs.minio.io/docs/minio-client-complete-guide#events) APIs) - BucketRequestPayment - BucketTagging #### List of Amazon S3 Object API's not supported on Minio -- ObjectACL (Use [bucket policies](http://docs.minio.io/docs/minio-client-complete-guide#policy) instead) +- ObjectACL (Use [bucket policies](https://docs.minio.io/docs/minio-client-complete-guide#policy) instead) - ObjectTorrent - ObjectVersions diff --git a/docs/orchestration/README.md b/docs/orchestration/README.md index 5f0ac24e6..a43d53e20 100644 --- a/docs/orchestration/README.md +++ b/docs/orchestration/README.md @@ -4,10 +4,10 @@ Minio is a cloud-native application designed to scale in a sustainable manner in | Orchestration platforms| |:---| -| [`Docker Swarm`](http://docs.minio.io/docs/deploy-minio-on-docker-swarm) | -| [`Docker Compose`](http://docs.minio.io/docs/deploy-minio-on-docker-compose) | -| [`Kubernetes`](http://docs.minio.io/docs/deploy-minio-on-kubernetes) | -| [`DC/OS`](http://docs.minio.io/docs/deploy-minio-on-dc-os) | +| [`Docker Swarm`](https://docs.minio.io/docs/deploy-minio-on-docker-swarm) | +| [`Docker Compose`](https://docs.minio.io/docs/deploy-minio-on-docker-compose) | +| [`Kubernetes`](https://docs.minio.io/docs/deploy-minio-on-kubernetes) | +| [`DC/OS`](https://docs.minio.io/docs/deploy-minio-on-dc-os) | ## Why is Minio cloud-native? The term cloud-native revolves around the idea of applications deployed as micro services, that scale well. It is not about just retrofitting monolithic applications onto modern container based compute environment. A cloud-native application is portable and resilient by design, and can scale horizontally by simply replicating. Modern orchestration platforms like Swarm, Kubernetes and DC/OS make replicating and managing containers in huge clusters easier than ever. diff --git a/docs/zh_CN/bucket/notifications/README.md b/docs/zh_CN/bucket/notifications/README.md index a26069c3e..84dbb6871 100644 --- a/docs/zh_CN/bucket/notifications/README.md +++ b/docs/zh_CN/bucket/notifications/README.md @@ -16,8 +16,8 @@ ## 前提条件 -* 从[这里](http://docs.minio.io/docs/zh_CN/minio-quickstart-guide)下载并安装Minio Server。 -* 从[这里](https://docs.minio.io/docs/zh_CN/minio-client-quickstart-guide)下载并安装Minio Client。 +* 从[这里](https://docs.minio.io/cn/minio-quickstart-guide)下载并安装Minio Server。 +* 从[这里](https://docs.minio.io/cn/minio-client-quickstart-guide)下载并安装Minio Client。 ## 使用AMQP发布Minio事件 @@ -960,4 +960,4 @@ mc ls myminio/images-thumbnail [2017-02-08 11:39:40 IST] 992B images-thumbnail.jpg ``` -*注意* 如果你用的是 [distributed Minio](https://docs.minio.io/docs/zh_CN/distributed-minio-quickstart-guide),请修改所有节点的 ``~/.minio/config.json``。 +*注意* 如果你用的是 [distributed Minio](https://docs.minio.io/cn/distributed-minio-quickstart-guide),请修改所有节点的 ``~/.minio/config.json``。 diff --git a/docs/zh_CN/config/README.md b/docs/zh_CN/config/README.md index fb36a4fe9..c17c2e337 100644 --- a/docs/zh_CN/config/README.md +++ b/docs/zh_CN/config/README.md @@ -10,7 +10,7 @@ minio server --config-dir /etc/minio /data ``` ### 证书目录 -TLS证书存在``${HOME}/.minio/certs``目录下，你需要将证书放在该目录下来启用`HTTPS` 。如果你是一个乐学上进的好青年，这里有一本免费的秘籍传授一你: [如何使用TLS安全的访问minio](http://docs.minio.io/docs/zh_CN/how-to-secure-access-to-minio-server-with-tls). +TLS证书存在``${HOME}/.minio/certs``目录下，你需要将证书放在该目录下来启用`HTTPS` 。如果你是一个乐学上进的好青年，这里有一本免费的秘籍传授一你: [如何使用TLS安全的访问minio](https://docs.minio.io/cn/how-to-secure-access-to-minio-server-with-tls). 以下是一个带来TLS证书的Minio server的目录结构。 @@ -73,14 +73,14 @@ minio server /data |参数|类型|描述| |:---|:---|:---| |``notify``| |通知通过以下方式开启存储桶事件通知，用于lambda计算| -|``notify.amqp``| |[通过AMQP发布Minio事件](http://docs.minio.io/docs/zh_CN/minio-bucket-notification-guide#AMQP)| -|``notify.mqtt``| |[通过MQTT发布Minio事件](http://docs.minio.io/docs/zh_CN/minio-bucket-notification-guide#MQTT)| -|``notify.elasticsearch``| |[通过Elasticsearch发布Minio事件](http://docs.minio.io/docs/zh_CN/minio-bucket-notification-guide#Elasticsearch)| -|``notify.redis``| |[通过Redis发布Minio事件](http://docs.minio.io/docs/zh_CN/minio-bucket-notification-guide#Redis)| -|``notify.nats``| |[通过NATS发布Minio事件](http://docs.minio.io/docs/zh_CN/minio-bucket-notification-guide#NATS)| -|``notify.postgresql``| |[通过PostgreSQL发布Minio事件](http://docs.minio.io/docs/zh_CN/minio-bucket-notification-guide#PostgreSQL)| -|``notify.kafka``| |[通过Apache Kafka发布Minio事件](http://docs.minio.io/docs/zh_CN/minio-bucket-notification-guide#apache-kafka)| -|``notify.webhook``| |[通过Webhooks发布Minio事件](http://docs.minio.io/docs/zh_CN/minio-bucket-notification-guide#webhooks)| +|``notify.amqp``| |[通过AMQP发布Minio事件](https://docs.minio.io/cn/minio-bucket-notification-guide#AMQP)| +|``notify.mqtt``| |[通过MQTT发布Minio事件](https://docs.minio.io/cn/minio-bucket-notification-guide#MQTT)| +|``notify.elasticsearch``| |[通过Elasticsearch发布Minio事件](https://docs.minio.io/cn/minio-bucket-notification-guide#Elasticsearch)| +|``notify.redis``| |[通过Redis发布Minio事件](https://docs.minio.io/cn/minio-bucket-notification-guide#Redis)| +|``notify.nats``| |[通过NATS发布Minio事件](https://docs.minio.io/cn/minio-bucket-notification-guide#NATS)| +|``notify.postgresql``| |[通过PostgreSQL发布Minio事件](https://docs.minio.io/cn/minio-bucket-notification-guide#PostgreSQL)| +|``notify.kafka``| |[通过Apache Kafka发布Minio事件](https://docs.minio.io/cn/minio-bucket-notification-guide#apache-kafka)| +|``notify.webhook``| |[通过Webhooks发布Minio事件](https://docs.minio.io/cn/minio-bucket-notification-guide#webhooks)| ## 了解更多 * [Minio Quickstart Guide](https://docs.minio.io/docs/minio-quickstart-guide) diff --git a/docs/zh_CN/distributed/README.md b/docs/zh_CN/distributed/README.md index 218a461a6..dab7f04d5 100644 --- a/docs/zh_CN/distributed/README.md +++ b/docs/zh_CN/distributed/README.md @@ -8,7 +8,7 @@ ### 数据保护 -分布式Minio采用 [erasure code](https://docs.minio.io/docs/zh_CN/minio-erasure-code-quickstart-guide)来防范多个节点宕机和[位衰减`bit rot`](https://github.com/minio/minio/blob/master/docs/zh_CN/erasure/README.md#what-is-bit-rot-protection)。 +分布式Minio采用 [erasure code](https://docs.minio.io/cn/minio-erasure-code-quickstart-guide)来防范多个节点宕机和[位衰减`bit rot`](https://github.com/minio/minio/blob/master/cn/erasure/README.md#what-is-bit-rot-protection)。 分布式Minio至少需要4个节点，使用分布式Minio自动引入了纠删码功能。 ### 高可用 @@ -33,7 +33,7 @@ Minio在分布式和单机模式下，所有读写操作都严格遵守**read-af ## 1. 前提条件 -安装Minio - [Minio快速入门](https://docs.minio.io/docs/zh_CN/minio-quickstart-guide). +安装Minio - [Minio快速入门](https://docs.minio.io/cn/minio-quickstart-guide). ## 2. 运行分布式Minio @@ -108,12 +108,12 @@ minio.exe server http://192.168.1.11/C:/data1 http://192.168.1.11/C:/data2 ^ ## 3. 验证 -验证是否部署成功，使用浏览器访问Minio服务或者使用 [`mc`](https://docs.minio.io/docs/zh_CN/minio-client-quickstart-guide)。多个节点的存储容量和就是分布式Minio的存储容量。 +验证是否部署成功，使用浏览器访问Minio服务或者使用 [`mc`](https://docs.minio.io/cn/minio-client-quickstart-guide)。多个节点的存储容量和就是分布式Minio的存储容量。 ## 了解更多 -- [Minio纠删码快速入门](https://docs.minio.io/docs/zh_CN/minio-erasure-code-quickstart-guide) -- [使用 `mc`](https://docs.minio.io/docs/zh_CN/minio-client-quickstart-guide) -- [使用 `aws-cli`](https://docs.minio.io/docs/zh_CN/aws-cli-with-minio) -- [使用 `s3cmd](https://docs.minio.io/docs/zh_CN/s3cmd-with-minio) -- [使用 `minio-go` SDK ](https://docs.minio.io/docs/zh_CN/golang-client-quickstart-guide) +- [Minio纠删码快速入门](https://docs.minio.io/cn/minio-erasure-code-quickstart-guide) +- [使用 `mc`](https://docs.minio.io/cn/minio-client-quickstart-guide) +- [使用 `aws-cli`](https://docs.minio.io/cn/aws-cli-with-minio) +- [使用 `s3cmd](https://docs.minio.io/cn/s3cmd-with-minio) +- [使用 `minio-go` SDK ](https://docs.minio.io/cn/golang-client-quickstart-guide) - [minio官方文档](https://docs.minio.io) diff --git a/docs/zh_CN/docker/README.md b/docs/zh_CN/docker/README.md index 66930d752..98a4e6f36 100644 --- a/docs/zh_CN/docker/README.md +++ b/docs/zh_CN/docker/README.md @@ -29,7 +29,7 @@ docker run -p 9000:9000 --name minio1 \ ``` ## 在Docker中运行Minio分布式模式 -分布式Minio可以通过 [Docker Compose](https://docs.minio.io/docs/zh_CN/deploy-minio-on-docker-compose) 或者 [Swarm mode](https://docs.minio.io/docs/zh_CN/deploy-minio-on-docker-swarm)进行部署。这两者之间的主要区别是Docker Compose创建了单个主机，多容器部署，而Swarm模式创建了一个多主机，多容器部署。 +分布式Minio可以通过 [Docker Compose](https://docs.minio.io/cn/deploy-minio-on-docker-compose) 或者 [Swarm mode](https://docs.minio.io/cn/deploy-minio-on-docker-swarm)进行部署。这两者之间的主要区别是Docker Compose创建了单个主机，多容器部署，而Swarm模式创建了一个多主机，多容器部署。 这意味着Docker Compose可以让你快速的在你的机器上快速使用分布式Minio-非常适合开发，测试环境；而Swarm模式提供了更健壮，生产级别的部署。 @@ -110,7 +110,7 @@ docker stats ## 了解更多 -* [在Docker Compose上部署Minio](https://docs.minio.io/docs/zh_CN/deploy-minio-on-docker-compose) -* [在Docker Swarm上部署Minio](https://docs.minio.io/docs/zh_CN/deploy-minio-on-docker-swarm) -* [分布式Minio快速入门](https://docs.minio.io/docs/zh_CN/distributed-minio-quickstart-guide) -* [Minio纠删码模式快速入门](https://docs.minio.io/docs/zh_CN/minio-erasure-code-quickstart-guide) +* [在Docker Compose上部署Minio](https://docs.minio.io/cn/deploy-minio-on-docker-compose) +* [在Docker Swarm上部署Minio](https://docs.minio.io/cn/deploy-minio-on-docker-swarm) +* [分布式Minio快速入门](https://docs.minio.io/cn/distributed-minio-quickstart-guide) +* [Minio纠删码模式快速入门](https://docs.minio.io/cn/minio-erasure-code-quickstart-guide) diff --git a/docs/zh_CN/erasure/README.md b/docs/zh_CN/erasure/README.md index 12156fc82..76914f367 100644 --- a/docs/zh_CN/erasure/README.md +++ b/docs/zh_CN/erasure/README.md @@ -20,7 +20,7 @@ Minio使用纠删码`erasure code`和校验和`checksum`来保护数据免受硬 ### 1. 前提条件: -安装Minio- [Minio快速入门](https://docs.minio.io/docs/zh_CN/minio-quickstart-guide) +安装Minio- [Minio快速入门](https://docs.minio.io/cn/minio-quickstart-guide) ### 2. 以纠删码模式运行Minio diff --git a/docs/zh_CN/gateway/azure.md b/docs/zh_CN/gateway/azure.md index 25e37f15a..9da6d15c2 100644 --- a/docs/zh_CN/gateway/azure.md +++ b/docs/zh_CN/gateway/azure.md @@ -41,7 +41,7 @@ mc ls myazure [限制](https://github.com/minio/minio/blob/master/docs/gateway/azure-limitations.md) ## 了解更多 -- [`mc` 命令行接口](https://docs.minio.io/docs/zh_CN/minio-client-quickstart-guide) -- [`aws` 命令行接口](https://docs.minio.io/docs/zh_CN/aws-cli-with-minio) -- [`minfs` 文件系统接口](http://docs.minio.io/docs/zh_CN/minfs-quickstart-guide) -- [`minio-go` Go SDK](https://docs.minio.io/docs/zh_CN/golang-client-quickstart-guide) +- [`mc` 命令行接口](https://docs.minio.io/cn/minio-client-quickstart-guide) +- [`aws` 命令行接口](https://docs.minio.io/cn/aws-cli-with-minio) +- [`minfs` 文件系统接口](https://docs.minio.io/cn/minfs-quickstart-guide) +- [`minio-go` Go SDK](https://docs.minio.io/cn/golang-client-quickstart-guide) diff --git a/docs/zh_CN/gateway/gcs.md b/docs/zh_CN/gateway/gcs.md index 494b4f81b..f239149b8 100644 --- a/docs/zh_CN/gateway/gcs.md +++ b/docs/zh_CN/gateway/gcs.md @@ -56,8 +56,8 @@ mc ls mygcs [限制](https://github.com/minio/minio/blob/master/docs/gateway/gcs-limitations.md) ## 了解更多 -- [`mc` 命令行接口](https://docs.minio.io/docs/zh_CN/minio-client-quickstart-guide) -- [`aws` 命令行接口](https://docs.minio.io/docs/zh_CN/aws-cli-with-minio) -- [`minfs` 文件系统接口](http://docs.minio.io/docs/zh_CN/minfs-quickstart-guide) -- [`minio-go` Go SDK](https://docs.minio.io/docs/zh_CN/golang-client-quickstart-guide) +- [`mc` 命令行接口](https://docs.minio.io/cn/minio-client-quickstart-guide) +- [`aws` 命令行接口](https://docs.minio.io/cn/aws-cli-with-minio) +- [`minfs` 文件系统接口](https://docs.minio.io/cn/minfs-quickstart-guide) +- [`minio-go` Go SDK](https://docs.minio.io/cn/golang-client-quickstart-guide) diff --git a/docs/zh_CN/minio-limits.md b/docs/zh_CN/minio-limits.md index df3737d8b..6cfbeec4e 100644 --- a/docs/zh_CN/minio-limits.md +++ b/docs/zh_CN/minio-limits.md @@ -35,17 +35,17 @@ ### Minio不支持的Amazon S3 Bucket API -- BucketACL (可以用 [bucket policies](http://docs.minio.io/docs/minio-client-complete-guide#policy)) +- BucketACL (可以用 [bucket policies](https://docs.minio.io/docs/minio-client-complete-guide#policy)) - BucketCORS (所有HTTP方法的所有存储桶都默认启用CORS) - BucketLifecycle (Minio纠删码不需要) -- BucketReplication (可以用 [`mc mirror`](http://docs.minio.io/docs/minio-client-complete-guide#mirror)) +- BucketReplication (可以用 [`mc mirror`](https://docs.minio.io/docs/minio-client-complete-guide#mirror)) - BucketVersions, BucketVersioning (可以用 [`s3git`](https://github.com/s3git/s3git)) - BucketWebsite (可以用 [`caddy`](https://github.com/mholt/caddy) or [`nginx`](https://www.nginx.com/resources/wiki/)) -- BucketAnalytics, BucketMetrics, BucketLogging (可以用 [bucket notification](http://docs.minio.io/docs/minio-client-complete-guide#events) APIs) +- BucketAnalytics, BucketMetrics, BucketLogging (可以用 [bucket notification](https://docs.minio.io/docs/minio-client-complete-guide#events) APIs) - BucketRequestPayment - BucketTagging ### Minio不支持的Amazon S3 Object API. -- ObjectACL (可以用 [bucket policies](http://docs.minio.io/docs/minio-client-complete-guide#policy)) +- ObjectACL (可以用 [bucket policies](https://docs.minio.io/docs/minio-client-complete-guide#policy)) - ObjectTorrent diff --git a/docs/zh_CN/multi-tenancy/README.md b/docs/zh_CN/multi-tenancy/README.md index 997257fd5..e8c86b749 100644 --- a/docs/zh_CN/multi-tenancy/README.md +++ b/docs/zh_CN/multi-tenancy/README.md @@ -50,6 +50,6 @@ minio --config-dir ~/tenant3 server --address :9003 http://192.168.10.11/data/te ![示例3](https://github.com/minio/minio/blob/master/docs/screenshots/Example-3.jpg?raw=true) ## 云端可伸缩部署 -对于大型多租户Minio部署，我们建议使用一个流行的容器编排平台，比如Kubernetes、DC/OS，或者是Docker Swarm.参考 [这个文档](https://docs.minio.io/docs/zh_CN/minio-deployment-quickstart-guide) ,学习如何在编排平台中使用Minio。 +对于大型多租户Minio部署，我们建议使用一个流行的容器编排平台，比如Kubernetes、DC/OS，或者是Docker Swarm.参考 [这个文档](https://docs.minio.io/cn/minio-deployment-quickstart-guide) ,学习如何在编排平台中使用Minio。 diff --git a/docs/zh_CN/orchestration/README.md b/docs/zh_CN/orchestration/README.md index 0c2b00f64..0b343e247 100644 --- a/docs/zh_CN/orchestration/README.md +++ b/docs/zh_CN/orchestration/README.md @@ -5,10 +5,10 @@ Minio is a cloud-native application designed to scale in a sustainable manner in | Orchestration平台| |:---| -| [`Docker Swarm`](http://docs.minio.io/docs/zh_CN/deploy-minio-on-docker-swarm) | -| [`Docker Compose`](http://docs.minio.io/docs/zh_CN/deploy-minio-on-docker-compose) | -| [`Kubernetes`](http://docs.minio.io/docs/zh_CN/deploy-minio-on-kubernetes) | -| [`DC/OS`](http://docs.minio.io/docs/zh_CN/deploy-minio-on-dc-os) | +| [`Docker Swarm`](https://docs.minio.io/cn/deploy-minio-on-docker-swarm) | +| [`Docker Compose`](https://docs.minio.io/cn/deploy-minio-on-docker-compose) | +| [`Kubernetes`](https://docs.minio.io/cn/deploy-minio-on-kubernetes) | +| [`DC/OS`](https://docs.minio.io/cn/deploy-minio-on-dc-os) | ## 为什么说Minio是云原生的（cloud-native）? 云原生这个词代表的是一些思想的集合，比如微服务部署，可伸缩，而不是说把一个单体应用改造成容器部署。一个云原生的应用在设计时就考虑了移植性和可伸缩性，而且可以通过简单的复制即可实现水平扩展。现在兴起的编排平台，想Swarm,Kubernetes,以及DC/OS，让大规模集群的复制和管理变得前所未有的简单，哪里不会点哪里。 diff --git a/docs/zh_CN/orchestration/dcos/README.md b/docs/zh_CN/orchestration/dcos/README.md index dcb1545b1..54b3e5e36 100644 --- a/docs/zh_CN/orchestration/dcos/README.md +++ b/docs/zh_CN/orchestration/dcos/README.md @@ -38,6 +38,6 @@ $ dcos package uninstall minio ### 了解更多 -- [Minio Erasure Code QuickStart Guide](https://docs.minio.io/docs/zh_CN/minio-erasure-code-quickstart-guide) +- [Minio Erasure Code QuickStart Guide](https://docs.minio.io/cn/minio-erasure-code-quickstart-guide) - [DC/OS Project](https://docs.mesosphere.com/) diff --git a/docs/zh_CN/orchestration/docker-compose/README.md b/docs/zh_CN/orchestration/docker-compose/README.md index 6c9182217..38168588d 100644 --- a/docs/zh_CN/orchestration/docker-compose/README.md +++ b/docs/zh_CN/orchestration/docker-compose/README.md @@ -38,12 +38,12 @@ docker-compose.exe up * 更新每个服务中的命令部分。 * 更新要为新服务公开的端口号。 另外，请确保分配给新服务的端口尚未使用。 - 关于分布式Minio的更多资料，请访问[这里](https://docs.minio.io/docs/zh_CN/distributed-minio-quickstart-guide). + 关于分布式Minio的更多资料，请访问[这里](https://docs.minio.io/cn/distributed-minio-quickstart-guide). * Docker compose file中的Minio服务使用的端口是9001到9004，这允许多个服务在主机上运行。 ### 了解更多 - [Docker Compose概述](https://docs.docker.com/compose/overview/) -- [Minio Docker快速入门](https://docs.minio.io/docs/zh_CN/minio-docker-quickstart-guide) -- [使用Docker Swarm部署Minio](https://docs.minio.io/docs/zh_CN/deploy-minio-on-docker-swarm) -- [Minio纠删码快速入门](https://docs.minio.io/docs/zh_CN/minio-erasure-code-quickstart-guide) +- [Minio Docker快速入门](https://docs.minio.io/cn/minio-docker-quickstart-guide) +- [使用Docker Swarm部署Minio](https://docs.minio.io/cn/deploy-minio-on-docker-swarm) +- [Minio纠删码快速入门](https://docs.minio.io/cn/minio-erasure-code-quickstart-guide) diff --git a/docs/zh_CN/orchestration/docker-swarm/README.md b/docs/zh_CN/orchestration/docker-swarm/README.md index 4488e8d1c..f4a1bb30e 100644 --- a/docs/zh_CN/orchestration/docker-swarm/README.md +++ b/docs/zh_CN/orchestration/docker-swarm/README.md @@ -42,7 +42,7 @@ docker stack deploy --compose-file=docker-compose-secrets.yaml minio_stack 这将把Compose file里描述的服务部署为Docker stack`minio_stack`。 更多 `docker stack` [命令参考](https://docs.docker.com/engine/reference/commandline/stack/)。 -在stack成功部署之后，你可以通过[Minio Client](https://docs.minio.io/docs/zh_CN/minio-client-complete-guide) `mc` 或者浏览器访问http://[Node_Public_IP_Address]:[Expose_Port_on_Host]来访问你的Minio server。 +在stack成功部署之后，你可以通过[Minio Client](https://docs.minio.io/cn/minio-client-complete-guide) `mc` 或者浏览器访问http://[Node_Public_IP_Address]:[Expose_Port_on_Host]来访问你的Minio server。 ## 4. 删除分布式Minio services @@ -71,7 +71,7 @@ docker volume rm volume_name * 更新每个服务中的命令部分。 * 更新要为新服务公开的端口号。 另外，请确保分配给新服务的端口尚未使用。 - 关于分布式Minio的更多资料，请访问[这里](https://docs.minio.io/docs/zh_CN/distributed-minio-quickstart-guide). + 关于分布式Minio的更多资料，请访问[这里](https://docs.minio.io/cn/distributed-minio-quickstart-guide). * 默认情况下，Minio服务使用的是`local` volume driver. 更多配置选项，请访问[Docker documentation](https://docs.docker.com/compose/compose-file/#/volume-configuration-reference) 。 @@ -81,6 +81,6 @@ docker volume rm volume_name ### 了解更多 - [Docker Swarm mode概述](https://docs.docker.com/engine/swarm/) -- [Minio Docker快速入门](https://docs.minio.io/docs/zh_CN/minio-docker-quickstart-guide) -- [使用Docker Compose部署Minio](https://docs.minio.io/docs/zh_CN/deploy-minio-on-docker-compose) -- [Minio纠删码快速入门](https://docs.minio.io/docs/zh_CN/minio-erasure-code-quickstart-guide) +- [Minio Docker快速入门](https://docs.minio.io/cn/minio-docker-quickstart-guide) +- [使用Docker Compose部署Minio](https://docs.minio.io/cn/deploy-minio-on-docker-compose) +- [Minio纠删码快速入门](https://docs.minio.io/cn/minio-erasure-code-quickstart-guide) diff --git a/docs/zh_CN/orchestration/kubernetes-yaml/README.md b/docs/zh_CN/orchestration/kubernetes-yaml/README.md index aed973cc4..823844b45 100644 --- a/docs/zh_CN/orchestration/kubernetes-yaml/README.md +++ b/docs/zh_CN/orchestration/kubernetes-yaml/README.md @@ -202,7 +202,7 @@ kubectl delete deployment minio-deployment \ ## Minio分布式服务部署 -以下文档介绍了在Kubernetes上部署[分布式Minio](https://docs.minio.io/docs/zh_CN/distributed-minio-quickstart-guide)服务器的过程。 本示例使用Docker Hub的[官方Minio Docker镜像](https://hub.docker.com/r/minio/minio/~/dockerfile/)。 +以下文档介绍了在Kubernetes上部署[分布式Minio](https://docs.minio.io/cn/distributed-minio-quickstart-guide)服务器的过程。 本示例使用Docker Hub的[官方Minio Docker镜像](https://hub.docker.com/r/minio/minio/~/dockerfile/)。 此示例使用以下Kubernetes的核心组件： diff --git a/docs/zh_CN/orchestration/kubernetes/README.md b/docs/zh_CN/orchestration/kubernetes/README.md index c36b34134..329ac3195 100644 --- a/docs/zh_CN/orchestration/kubernetes/README.md +++ b/docs/zh_CN/orchestration/kubernetes/README.md @@ -64,7 +64,7 @@ $ helm install --name my-release -f values.yaml stable/minio ### 分布式Minio -默认情况下，此图表以独立模式提供Minio服务器。 要在[分布式模式](https://docs.minio.io/docs/zh_CN/distributed-minio-quickstart-guide)中配置Minio服务器，请将`mode`字段设置为`distributed`, +默认情况下，此图表以独立模式提供Minio服务器。 要在[分布式模式](https://docs.minio.io/cn/distributed-minio-quickstart-guide)中配置Minio服务器，请将`mode`字段设置为`distributed`, ```bash $ helm install --set mode=distributed stable/minio @@ -150,6 +150,6 @@ $ helm install --set accessKey=myaccesskey,secretKey=mysecretkey \ ``` ### 了解更多 -- [Minio纠删码快速入门](https://docs.minio.io/docs/zh_CN/minio-erasure-code-quickstart-guide) +- [Minio纠删码快速入门](https://docs.minio.io/cn/minio-erasure-code-quickstart-guide) - [Kubernetes文档](https://kubernetes.io/docs/home/) - [Helm package manager for kubernetes](https://helm.sh/) diff --git a/docs/zh_CN/shared-backend/README.md b/docs/zh_CN/shared-backend/README.md index 463cfe631..75997e471 100644 --- a/docs/zh_CN/shared-backend/README.md +++ b/docs/zh_CN/shared-backend/README.md @@ -17,7 +17,7 @@ Minio共享模式是为了解决在真实场景中存在的一些问题，而且 ## 1. 前提条件 -安装Minio - [Minio快速入门](https://docs.minio.io/docs/zh_CN/minio). +安装Minio - [Minio快速入门](https://docs.minio.io/cn/minio). ## 2. 在共享后端存储上运行Minio @@ -61,11 +61,11 @@ minio.exe gateway nas M:\export ## 3. 验证 -为了验证部署是否成功，可能通过浏览器或者[`mc`](https://docs.minio.io/docs/zh_CN/minio-client-quickstart-guide)访问Minio。你应该可以从各个Minio节点访问上传的文件。 +为了验证部署是否成功，可能通过浏览器或者[`mc`](https://docs.minio.io/cn/minio-client-quickstart-guide)访问Minio。你应该可以从各个Minio节点访问上传的文件。 ## 了解更多 -- [使用`mc`](https://docs.minio.io/docs/zh_CN/minio-client-quickstart-guide) -- [使用`aws-cli`](https://docs.minio.io/docs/zh_CN/aws-cli-with-minio) -- [使用`s3cmd`](https://docs.minio.io/docs/zh_CN/s3cmd-with-minio) -- [使用`minio-go` SDK](https://docs.minio.io/docs/zh_CN/golang-client-quickstart-guide) +- [使用`mc`](https://docs.minio.io/cn/minio-client-quickstart-guide) +- [使用`aws-cli`](https://docs.minio.io/cn/aws-cli-with-minio) +- [使用`s3cmd`](https://docs.minio.io/cn/s3cmd-with-minio) +- [使用`minio-go` SDK](https://docs.minio.io/cn/golang-client-quickstart-guide) - [Minio文档](https://docs.minio.io) diff --git a/docs/zh_CN/tls/README.md b/docs/zh_CN/tls/README.md index e8fa3a83d..c6da249c2 100644 --- a/docs/zh_CN/tls/README.md +++ b/docs/zh_CN/tls/README.md @@ -20,7 +20,7 @@ Minio在Linux只支持使用PEM格式的key/certificate。 #### 使用 Let's Encrypt -更多信息，请访问 [这里](https://docs.minio.io/docs/zh_CN/generate-let-s-encypt-certificate-using-concert-for-minio) +更多信息，请访问 [这里](https://docs.minio.io/cn/generate-let-s-encypt-certificate-using-concert-for-minio) #### 使用 generate_cert.go (self-signed certificate) @@ -125,5 +125,5 @@ certtool.exe --generate-self-signed --load-privkey private.key --template cert.c Minio可以配置成连接其它服务，不管是Minio节点还是像NATs、Redis这些。如果这些服务用的不是在已知证书机构注册的证书，你可以让Minio服务信任这些CA，怎么做呢，将这些证书放到Minio配置路径下(`~/.minio/certs/CAs/` Linux 或者 `C:\Users\\.minio\certs\CAs` Windows). # 了解更多 -* [Minio快速入门](https://docs.minio.io/docs/zh_CN/minio-quickstart-guide) -* [Minio客户端权威指南](https://docs.minio.io/docs/zh_CN/minio-client-complete-guide) +* [Minio快速入门](https://docs.minio.io/cn/minio-quickstart-guide) +* [Minio客户端权威指南](https://docs.minio.io/cn/minio-client-complete-guide) diff --git a/pkg/madmin/config-commands.go b/pkg/madmin/config-commands.go index cf120c68e..dd9d09e06 100644 --- a/pkg/madmin/config-commands.go +++ b/pkg/madmin/config-commands.go @@ -59,7 +59,7 @@ func (adm *AdminClient) GetConfig() ([]byte, error) { return nil, httpRespToErrorResponse(resp) } - // Return the JSON marshalled bytes to user. + // Return the JSON marshaled bytes to user. return ioutil.ReadAll(resp.Body) }