From fd7ac55358cf55c4d150ef52db6ee89f10b87ca9 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Thu, 7 Jun 2018 21:18:43 -0700 Subject: [PATCH] Updated Directories and Files (markdown) --- Directories-and-Files.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/Directories-and-Files.md b/Directories-and-Files.md index fe11c6b..22361dc 100644 --- a/Directories-and-Files.md +++ b/Directories-and-Files.md @@ -4,6 +4,8 @@ When talking about file systems, many people would assume directories, list file ### Sample usage +First, run ```weed filer -h``` to see an example ```filer.toml``` file. Copy it out and read it, create the data store if needed. + Two ways to start a weed filer ```bash @@ -74,9 +76,9 @@ Here is a comparison of different filer store options. 1. "memory" : only for testing/example purpose. 2. "leveldb": simple, single machine, fast, scalable, but no failover. -3. "mysql"/"postgres": robust and common, fast enough for most cases, scalable. -4. "cassandra": robust and common, fast, scalable. -5. "redis": very fast, scalable with clustering, need to enable persistent storage, file listing is limited as one directory's sub file names are stored in one set of a key. +3. "mysql"/"postgres": robust and well-understood, fast enough for most cases, scalable. +4. "cassandra": robust and well-understood, fast, scalable. +5. "redis": very fast, scalable with clustering, need to enable persistent storage, file listing is limited because one directory's sub file names are stored in one key~value entry. ### Extending Storage Options