1
0
mirror of https://github.com/pirate/ArchiveBox.git synced 2025-08-27 08:14:38 +02:00

fix archivebox paths

Nick Sweeting
2018-12-31 20:54:24 -05:00
parent 2fdc49b68c
commit baf760ada8

@@ -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. 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: Example configuration using `env` command:
```bash ```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 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. Improving this process is on the roadmap, in future versions you'll be able to pass a config file directly to the archive command.