From 8b51c16e2c7b73a571c04cc43cba78b54841dd12 Mon Sep 17 00:00:00 2001 From: Wine93 Date: Tue, 30 Apr 2019 03:23:34 +0000 Subject: [PATCH] doc: added suggestion for code style --- README.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 051d1935a..79f3ccf5e 100644 --- a/README.md +++ b/README.md @@ -363,7 +363,7 @@ GlusterFS hashes the path and filename into ids, and assigned to virtual volumes Ceph can be setup similar to SeaweedFS as a key->blob store. It is much more complicated, with the need to support layers on top of it. [Here is a more detailed comparison](https://github.com/chrislusf/seaweedfs/issues/120) -SeaweedFS has a centralized master group to look up free volumes, while Ceph uses hashing and metadata servers to locate its objects. Having a centralized master makes it easy to code and manage. +SeaweedFS has a centralized master group to look up free volumes, while Ceph uses hashing and metadata servers to locate its objects. Having a centralized master makes it easy to code and manage. Same as SeaweedFS, Ceph is also based on the object store RADOS. Ceph is rather complicated with mixed reviews. @@ -388,6 +388,12 @@ Other key features include: Erasure Encoding, JWT security. This is a super exciting project! And we need helpers and [support](https://www.patreon.com/seaweedfs)! +BTW, We suggest run the code style check script `util/gostd` before you push your branch to remote, it will make SeaweedFS easy to review, maintain and develop: + +``` +$ ./util/gostd +``` + [Back to TOC](#table-of-contents) ## Installation Guide ##