From 037b9000a50358072283a10d127f40ff0ea1f4da Mon Sep 17 00:00:00 2001 From: Nick Sweeting Date: Wed, 29 Jul 2020 18:24:26 -0400 Subject: [PATCH] Updated Usage (markdown) --- Usage.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/Usage.md b/Usage.md index c9a3d1a..a6c9184 100644 --- a/Usage.md +++ b/Usage.md @@ -24,9 +24,12 @@ All three of these ways of running ArchiveBox are equivalent and interchangeable: -- `archivebox [subcommand] [...args]` (using `pip install archivebox`) -- `archivebox run -v $PWD:/data nikisweeting/archivebox [subcommand] [...args]` (using the official Docker image) -- `docker-compose run archivebox [subcommand] [...args]` (using the official Docker image in a Docker Compose project) +- `archivebox [subcommand] [...args]` + *Using the PyPI package via `pip install archivebox`* +- `archivebox run -v $PWD:/data nikisweeting/archivebox [subcommand] [...args]` + *Using the official Docker image* +- `docker-compose run archivebox [subcommand] [...args]` + *Using the official Docker image w/ Docker Compose* You can share a single archivebox data directory between Docker and non-Docker instances as well, allowing you to run the server in a container but still execute CLI commands on the host for example.