From fd6fdbd3f9de119e9528f836f6d67bd951af3586 Mon Sep 17 00:00:00 2001
From: Quentin Machu <me@quentin-machu.fr>
Date: Thu, 14 Jan 2016 15:45:01 -0500
Subject: [PATCH] docs: update config example

---
 config.example.yaml | 17 +++++------------
 1 file changed, 5 insertions(+), 12 deletions(-)

diff --git a/config.example.yaml b/config.example.yaml
index 0c459632..c3741d2d 100644
--- a/config.example.yaml
+++ b/config.example.yaml
@@ -2,18 +2,11 @@
 # is specified or if the keys are not defined.
 ---
 database:
-  # Database backend.
-  #
-  # Possible values are "bolt", "leveldb", "memstore", "mongo", "sql".
-  #
-  # When running multiple instances is not desired, using BoltDB backend is the best choice as it is
-  # lightning fast. However, using PostgreSQL enables running multiple instances concurrently.
-  # The default is just an ephemeral database.
-  type: memstore
-  # Path to the database.
-  #
-  # Can be a file or a connection string.
-  path:
+  # PostgreSQL Connection string.
+  # Reference: http://www.postgresql.org/docs/9.4/static/libpq-connect.html
+  source: 
+  # Number of elements to keep in the cache.
+  cacheSize: 16384
 api:
   # Port on which the main API and the health API will listen on.
   port: 6060