diff options
| -rw-r--r-- | .project | 2 | ||||
| -rw-r--r-- | README.md | 7 |
2 files changed, 2 insertions, 7 deletions
@@ -1,6 +1,6 @@ <?xml version="1.0" encoding="UTF-8"?> <projectDescription> - <name>weed-fs</name> + <name>seaweedfs</name> <comment></comment> <projects> </projects> @@ -223,7 +223,7 @@ All file meta information on volume server is readable from memory without disk Frankly, I don't use other distributed file systems too often. All seems more complicated than necessary. Please correct me if anything here is wrong. ### Compared to Ceph ### -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://code.google.com/p/weed-fs/issues/detail?id=44 +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 is meant to be fast and simple, both during usage and during setup. If you do not understand how it works when you reach here, we failed! Jokes aside, you should not need any consulting service for it. @@ -286,11 +286,6 @@ once this is done, you should see the executable "weed" under $GOPATH/bin step 4: after you modify your code locally, you could start a local build by calling "go install" under $GOPATH/src/github.com/chrislusf/seaweedfs/go/weed -## Reference - -For pre-compiled releases, - https://bintray.com/chrislusf/Weed-FS/seaweed - ## Disk Related topics ## ### Hard Drive Performance ### |