From 61fa4ec2af945c498cd8de44a25483c6b926e6f8 Mon Sep 17 00:00:00 2001
From: Nick Sweeting <git@sweeting.me>
Date: Wed, 23 Jan 2019 01:43:48 -0500
Subject: [PATCH] Updated Configuration (markdown)

---
 Configuration.md | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/Configuration.md b/Configuration.md
index 2efa5e9..c3fde85 100644
--- a/Configuration.md
+++ b/Configuration.md
@@ -55,22 +55,23 @@ The chrome/chromium dependency is _optional_ and only required for screenshots,
 
 ## Creating a Config File
 
+To set up a persistent config:
 
-One way to have persistent config is to create a `~/.ArchiveBox.conf` file, and put your options inside it like so:
+1. Copy `etc/ArchiveBox.conf.default` to `~/.ArchiveBox.conf`
+```bash
+cp ArchiveBox/etc/ArchiveBox.conf.default ~/.ArchiveBox.conf
+```
 
+2. Edit your options inside `~/.ArchiveBox.conf`, e.g.:
 ```bash
 CHROME_BINARY=google-chrome-stable
 RESOLUTION=1440,900
 FETCH_PDF=False
 ```
 
-Then source it when you run the archive script:
-
+3. Source your config file when you run your archive script:
 ```bash
-env $(cat ~/.ArchiveBox.conf) ./archive https://example.com/rss/feed.xml
-
-# or if you have comments in your env file:
-export $(grep -v '^#' ~/.ArchiveBox.conf | xargs); ./archive https://example.com/rss/feed.xml
+export "$(grep -v '^#' ~/.ArchiveBox.conf | xargs)"; ./archive https://example.com/rss/feed.xml
 ```
 
 Improving this process is on the roadmap, in future versions you'll be able to pass a config file directly to the archive command.
\ No newline at end of file