From baf760ada8249abef066c0b070d4572001355d87 Mon Sep 17 00:00:00 2001 From: Nick Sweeting Date: Mon, 31 Dec 2018 20:54:24 -0500 Subject: [PATCH] fix archivebox paths --- Configuration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Configuration.md b/Configuration.md index 413aef1..81c4b5d 100644 --- a/Configuration.md +++ b/Configuration.md @@ -2,7 +2,7 @@ Configuration is done through environment variables. You can pass in settings using all the usual environment variable methods: e.g. by using the `env` command, settings variables in your shell profile, or sourcing a `.env` file before running the command. -You can also modify the defaults in `archiver/config.py` directly, but that's not recommended as your custom settings will be erased whenever you update ArchiveBox. +You can also modify the defaults in `archivebox/config.py` directly, but that's not recommended as your custom settings will be erased whenever you update ArchiveBox. Example configuration using `env` command: ```bash @@ -62,4 +62,4 @@ Then source it when you run the archive script: 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 +Improving this process is on the roadmap, in future versions you'll be able to pass a config file directly to the archive command.