From e83e9100e4081f2f419aefdc0179a45b70c5b29d Mon Sep 17 00:00:00 2001 From: Knut Ahlers Date: Wed, 29 Jul 2015 09:40:39 +0200 Subject: [PATCH] Added examples to the README --- README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index d8088c7..386a51d 100644 --- a/README.md +++ b/README.md @@ -31,7 +31,8 @@ What you definitely should set when starting the server: This storage engine is used in the default config when you just start up the server as you can see in the output above. You don't have many options to set for this one. The only thing is the path where all the data is stored. ``` -local:/// +Schema: local:/// +Example: local:///./data ``` The directory can be set absolute or relative. Please ensure there are **3** slashes between `local:` and the begin of your path. (So if you're setting an absolute path you will set 4 slashes in a row.) @@ -41,7 +42,8 @@ The directory can be set absolute or relative. Please ensure there are **3** sla This is the storage engine you want to use if you're migrating from the old CloudKeys version. This option is fully compatible to every piece of data the old version stored. ``` -s3:// +Schema: s3:// +Example: s3://mybucket/ ``` You can specify the bucket and also a prefix for the storage. That way you even could use one bucket for different instances of CloudKeys Go. In case you're migrating from the old version you need to set the path to `/`.