▶️ Make sure the dependencies are fully installed before running any ArchiveBox commands.
ArchiveBox API Reference:
- Overview: Program structure and outline of basic archiving process.
- CLI Usage: Docs and examples for the ArchiveBox command line interface.
- UI Usage: Docs and screenshots for the outputted HTML archive interface.
- Disk Layout: Description of the archive folder structure and contents.
- [[Docker]]: Learn about ArchiveBox usage with Docker and Docker Compose
- [[Configuration]]: Learn about the various archive method options
- [[Scheduled Archiving]]: Learn how to set up automatic daily archiving
- [[Publishing Your Archive]]: Learn how to host your archive for others to access
- [[Troubleshooting]]: Resources if you encounter any problems
- Screenshots: See what the CLI and outputted HTML look like
All three of these ways of running ArchiveBox are equivalent and interchangeable:
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.
For more examples see the [[Docker]] page.
- Run ArchiveBox with configuration options
- Import a single URL or list of URLs via stdin
- Import list of links exported from browser or another service
- Import list of URLs from a remote RSS feed or file
- Import list of links from browser history
Run ArchiveBox with configuration options¶
You can set environment variables in your shell profile, a config file, or by using the
# via the CLI archivebox config --set TIMEOUT=3600 # by modifying the config file nano ArchiveBox.conf # TIMEOUT=3600 # or by using environment variables env TIMEOUT=3600 archivebox add 'https://example.com'
See [[Configuration]] page for more details about the available options and ways to pass config.If you’re using Docker, also make sure to read the Configuration section on the [[Docker]] page.
Import a single URL¶
archivebox add 'https://example.com' # or echo 'https://example.com' | archivebox add
You can also add
--depth=1 to any of these commands if you want to recursively archive the URLs and all URLs one hop away. (e.g. all the outlinks on a page + the page).
Import a list of URLs from a txt file¶
cat urls_to_archive.txt | archivebox add # or archivebox add < urls_to_archive.txt # or curl https://getpocket.com/users/USERNAME/feed/all | archivebox add
You can also pipe in RSS, XML, Netscape, or any of the other supported import formats via stdin.
archivebox add < ~/Downloads/browser_bookmarks_export.html # or archivebox add < ~/Downloads/pinboard_bookmarks.json # or archivebox add < ~/Downloads/other_links.txt
archivebox server open http://127.0.0.1:8000
Or if you prefer to use the static HTML UI instead of the interactive UI provided by the server,
you can open
./index.html in a browser. You should see something like this.
You can sort by column, search using the box in the upper right, and see the total number of links at the bottom.
Click the Favicon under the “Files” column to go to the details page for each link.
OUTPUT_DIR folder (usually whatever folder you run
archivebox in), contains the UI HTML and archived data with the structure outlined below.
- output/ - index.sqlite3 # Main index of all archived URLs - index.json # Redundant JSON version of the same main index - index.html # Redundant static HTML version of the same main index - archive/ - 155243135/ # Archived links are stored in folders by timestamp - index.json # Index/details page for individual archived link - index.html # Archive method outputs: - warc/ - media/ - git/ ... - sources/ # Each imported URL list is saved as a copy here - getpocket.com-1552432264.txt - stdin-1552291774.txt ... - static/ # Staticfiles for the archive UI - robots.txt
I’ve found it takes about an hour to download 1000 articles, and they’ll take up roughly 1GB.Those numbers are from running it single-threaded on my i5 machine with 50mbps down. YMMV.
Storage requirements go up immensely if you’re using
FETCH_MEDIA=True and are archiving many pages with audio & video.
You can run it in parallel by manually splitting your URLs into separate chunks:
archivebox add < urls_chunk_1.txt & archivebox add < urls_chunk_2.txt & archivebox add < urls_chunk_3.txt &
(though this may not be faster if you have a very large collection/main index)
Users have reported running it with 50k+ bookmarks with success (though it will take more RAM while running).
If you already imported a huge list of bookmarks and want to import only new
bookmarks, you can use the
ONLY_NEW environment variable. This is useful if
you want to import a bookmark dump periodically and want to skip broken links
which are already in the index.
Python API Usage¶
from archivebox.main import add, info, remove, check_data_folder out_dir = '~/path/to/my/data/folder' check_data_folder(out_dir=out_dir) add('https://example.com', index_only=True, out_dir=out_dir) info(out_dir=out_dir) remove('https://example.com', delete=True, yes=True, out_dir=out_dir)
For more information see the Python API Reference.