Bookmark Archiver

ANNOUNCEMENT: SOON TO BE RENAMED, COMMENT HERE TO DISCUSS NEW NAMES.

"Your own personal Way-Back Machine"

Save an archived copy of the websites you visit (the actual content of each site, not just the list of links).

Can import links from:

Browser history or bookmarks (Chrome, Firefox, Safari, IE, Opera)
Pocket
Pinboard
RSS or plain text lists
Shaarli, Delicious, Instapaper, Reddit Saved Posts, Wallabag, Unmark.it, and more!

For each site, it outputs (configurable):

Browsable static HTML archive (wget)
PDF (Chrome headless)
Screenshot (Chrome headless)
HTML after 2s of JS running (Chrome headless)
Favicon
Submits URL to archive.org
Index summary pages: index.html & index.json

The archiving is additive, so you can schedule ./archive to run regularly and pull new links into the index. All the saved content is static and indexed with json files, so it lives forever & is easily parseable, it requires no always-running backend.

DEMO: archive.sweeting.me

Quickstart

1. Get your list of URLs:

Follow the links here to find instructions for exporting a list of URLs from each service.

Pocket
Pinboard
Instapaper
Reddit Saved Posts
Shaarli
Unmark.it
Wallabag
Chrome Bookmarks
Firefox Bookmarks
Safari Bookmarks
Opera Bookmarks
Internet Explorer Bookmarks
Chrome History: ./bin/export-browser-history --chrome
Firefox History: ./bin/export-browser-history --firefox
Other File or URL: (e.g. RSS feed) pass as second argument in the next step

(If any of these links are broken, please submit an issue and I'll fix it)

2. Create your archive:

git clone https://github.com/pirate/bookmark-archiver
cd bookmark-archiver/
./setup                                         # install all dependencies

# add a list of links from a file
./archive ~/Downloads/bookmark_export.html      # replace with the path to your export file or URL from step 1

# OR add a list of links from remote URL
./archive "https://getpocket.com/users/yourusername/feed/all"  # url to an RSS, html, or json links file

# OR add all the links from your browser history
./bin/export-browser-history --chrome           # works with --firefox as well, can take path to SQLite history db
./archive output/sources/chrome_history.json

# OR just continue archiving the existing links in the index
./archive   # at any point if you just want to continue archiving where you left off, without adding any new links

3. Done!

You can open output/index.html to view your archive. (favicons will appear next to each title once it has finished downloading)

If you want to host your archive somewhere to share it with other people, see the Publishing Your Archive section below.

4. (Optional) Schedule it to run every day

You can import links from any local file path or feed url by changing the second argument to archive.py. Bookmark Archiver will ignore links that are imported multiple times, it will keep the earliest version that it's seen. This means you can add multiple cron jobs to pull links from several different feeds or files each day, it will keep the index up-to-date without duplicate links.

This example archives a pocket RSS feed and an export file every 24 hours, and saves the output to a logfile.

0 24 * * * yourusername /opt/bookmark-archiver/archive https://getpocket.com/users/yourusername/feed/all > /var/log/bookmark_archiver_rss.log
0 24 * * * yourusername /opt/bookmark-archiver/archive /home/darth-vader/Desktop/bookmarks.html > /var/log/bookmark_archiver_firefox.log

(Add the above lines to /etc/crontab)

Next Steps

If you have any trouble, see the Troubleshooting section at the bottom.
If you'd like to customize options, see the Configuration section.

If you want something easier than running programs in the command-line, take a look at Pocket Premium (yay Mozilla!) and Pinboard Pro (yay independent developer!). Both offer easy-to-use bookmark archiving with full-text-search and other features.

Details

archive.py is a script that takes a Pocket-format, JSON-format, Netscape-format, or RSS-formatted list of links, and downloads a clone of each linked website to turn into a browsable archive that you can store locally or host online.

The archiver produces an output folder output/ containing an index.html, index.json, and archived copies of all the sites, organized by timestamp bookmarked. It's Powered by headless Chromium and good 'ol wget.

For each sites it saves:

wget of site, e.g. en.wikipedia.org/wiki/Example.html with .html appended if not present
output.pdf Printed PDF of site using headless chrome
screenshot.png 1440x900 screenshot of site using headless chrome
output.html DOM Dump of the HTML after rendering using headless chrome
archive.org.txt A link to the saved site on archive.org
audio/ and video/ for sites like youtube, soundcloud, etc. (using youtube-dl) (WIP)
code/ clone of any repository for github, bitbucket, or gitlab links (WIP)
index.json JSON index containing link info and archive details
index.html HTML index containing link info and archive details (optional fancy or simple index)

Wget doesn't work on sites you need to be logged into, but chrome headless does, see the Configuration* section for CHROME_USER_DATA_DIR.

Large Exports & Estimated Runtime:

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.

You can run it in parallel by using the resume feature, or by manually splitting export.html into multiple files:

./archive export.html 1498800000 &  # second argument is timestamp to resume downloading from
./archive export.html 1498810000 &
./archive export.html 1498820000 &
./archive export.html 1498830000 &

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.

Configuration

You can tweak parameters via environment variables, or by editing config.py directly:

env CHROME_BINARY=google-chrome-stable RESOLUTION=1440,900 FETCH_PDF=False ./archive ~/Downloads/bookmarks_export.html

Shell Options:

colorize console ouput: USE_COLOR value: [True]/False
show progress bar: SHOW_PROGRESS value: [True]/False
archive permissions: OUTPUT_PERMISSIONS values: [755]/644/...

Dependency Options:

path to Chrome: CHROME_BINARY values: [chromium-browser]//usr/local/bin/google-chrome/...
path to wget: WGET_BINARY values: [wget]//usr/local/bin/wget/...

Archive Options:

maximum allowed download time per link: TIMEOUT values: [60]/30/...
import only new links: ONLY_NEW values True/[False]
archive methods (values: [True]/False):
- fetch page with wget: FETCH_WGET
- fetch images/css/js with wget: FETCH_WGET_REQUISITES (True is highly recommended)
- print page as PDF: FETCH_PDF
- fetch a screenshot of the page: FETCH_SCREENSHOT
- fetch a DOM dump of the page: FETCH_DOM
- fetch a favicon for the page: FETCH_FAVICON
- submit the page to archive.org: SUBMIT_ARCHIVE_DOT_ORG
screenshot: RESOLUTION values: [1440,900]/1024,768/...
user agent: WGET_USER_AGENT values: [Wget/1.19.1]/"Mozilla/5.0 ..."/...
chrome profile: CHROME_USER_DATA_DIR values: [~/Library/Application\ Support/Google/Chrome/Default]//tmp/chrome-profile/... To capture sites that require a user to be logged in, you must specify a path to a chrome profile (which loads the cookies needed for the user to be logged in). If you don't have an existing chrome profile, create one with chromium-browser --disable-gpu --user-data-dir=/tmp/chrome-profile, and log into the sites you need. Then set CHROME_USER_DATA_DIR=/tmp/chrome-profile to make Bookmark Archiver use that profile.
output directory: OUTPUT_DIR values: [$REPO_DIR/output]//srv/www/bookmarks/... Optionally output the archives to an alternative directory.

(See defaults & more at the top of config.py)

To tweak the outputted html index file's look and feel, just edit the HTML files in archiver/templates/.

The chrome/chromium dependency is optional and only required for screenshots, PDF, and DOM dump output, it can be safely ignored if those three methods are disabled.

Publishing Your Archive

The archive produced by ./archive is suitable for serving on any provider that can host static html (e.g. github pages!).

You can also serve it from a home server or VPS by uploading the outputted output folder to your web directory, e.g. /var/www/bookmark-archiver and configuring your webserver.

Here's a sample nginx configuration that works to serve archive folders:

location / {
    alias       /path/to/bookmark-archiver/output/;
    index       index.html;
    autoindex   on;               # see directory listing upon clicking "The Files" links
    try_files   $uri $uri/ =404;
}

Make sure you're not running any content as CGI or PHP, you only want to serve static files!

Urls look like: https://archive.example.com/archive/1493350273/en.wikipedia.org/wiki/Dining_philosophers_problem.html

Security WARNING & Content Disclaimer

Re-hosting other people's content has security implications for any other sites sharing your hosting domain. Make sure you understand the dangers of hosting unknown archived CSS & JS files on your shared domain. Due to the security risk of serving some malicious JS you archived by accident, it's best to put this on a domain or subdomain of its own to keep cookies separate and slightly mitigate CSRF attacks and other nastiness.

You may also want to blacklist your archive in /robots.txt if you don't want to be publicly assosciated with all the links you archive via search engine results.

Be aware that some sites you archive may not allow you to rehost their content publicly for copyright reasons, it's up to you to host responsibly and respond to takedown requests appropriately.

Please modify the FOOTER_INFO config variable to add your contact info to the footer of your index.

Info & Motivation

This is basically an open-source version of Pocket Premium (which you should consider paying for!). I got tired of sites I saved going offline or changing their URLS, so I started archiving a copy of them locally now, similar to The Way-Back Machine provided by archive.org. Self hosting your own archive allows you to save PDFs & Screenshots of dynamic sites in addition to static html, something archive.org doesn't do.

Now I can rest soundly knowing important articles and resources I like wont dissapear off the internet.

My published archive as an example: archive.sweeting.me.

Manual Setup

If you don't like running random setup scripts off the internet (:+1:), you can follow these manual setup instructions.

1. Install dependencies: chromium >= 59, wget >= 1.16, python3 >= 3.5 (google-chrome >= v59 works fine as well)

If you already have Google Chrome installed, or wish to use that instead of Chromium, follow the Google Chrome Instructions.

# On Mac:
brew cask install chromium  # If you already have Google Chrome/Chromium in /Applications/, skip this command
brew install wget python3

echo -e '#!/bin/bash\n/Applications/Chromium.app/Contents/MacOS/Chromium "$@"' > /usr/local/bin/chromium-browser  # see instructions for google-chrome below
chmod +x /usr/local/bin/chromium-browser

# On Ubuntu/Debian:
apt install chromium-browser python3 wget

# Check that everything worked:
chromium-browser --version && which wget && which python3 && which curl && echo "[√] All dependencies installed."

2. Get your bookmark export file:

Follow the instruction links above in the "Quickstart" section to download your bookmarks export file.

3. Run the archive script:

Clone this repo git clone https://github.com/pirate/bookmark-archiver
cd bookmark-archiver/
./archive ~/Downloads/bookmarks_export.html

You may optionally specify a second argument to archive.py export.html 153242424324 to resume the archive update at a specific timestamp.

If you have any trouble, see the Troubleshooting section at the bottom.

Google Chrome Instructions:

I recommend Chromium instead of Google Chrome, since it's open source and doesn't send your data to Google. Chromium may have some issues rendering some sites though, so you're welcome to try Google-chrome instead. It's also easier to use Google Chrome if you already have it installed, rather than downloading Chromium all over.

Install & link google-chrome

# On Mac:
# If you already have Google Chrome in /Applications/, skip this brew command
brew cask install google-chrome
brew install wget python3

echo -e '#!/bin/bash\n/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome "$@"' > /usr/local/bin/google-chrome
chmod +x /usr/local/bin/google-chrome

# On Linux:
wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
sudo sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google-chrome.list'
apt update; apt install google-chrome-beta python3 wget

Set the environment variable CHROME_BINARY to google-chrome before running:

env CHROME_BINARY=google-chrome ./archive ~/Downloads/bookmarks_export.html

If you're having any trouble trying to set up Google Chrome or Chromium, see the Troubleshooting section below.

Troubleshooting

Dependencies

Python:

On some Linux distributions the python3 package might not be recent enough. If this is the case for you, resort to installing a recent enough version manually.

add-apt-repository ppa:fkrull/deadsnakes && apt update && apt install python3.6

If you still need help, the official Python docs are a good place to start.

Chromium/Google Chrome:

archive.py depends on being able to access a chromium-browser/google-chrome executable. The executable used defaults to chromium-browser but can be manually specified with the environment variable CHROME_BINARY:

env CHROME_BINARY=/usr/local/bin/chromium-browser ./archive ~/Downloads/bookmarks_export.html

Test to make sure you have Chrome on your $PATH with:

which chromium-browser || which google-chrome

If no executable is displayed, follow the setup instructions to install and link one of them.

If a path is displayed, the next step is to check that it's runnable:

chromium-browser --version || google-chrome --version

If no version is displayed, try the setup instructions again, or confirm that you have permission to access chrome.

If a version is displayed and it's <59, upgrade it:

apt upgrade chromium-browser -y
# OR
brew cask upgrade chromium-browser

If a version is displayed and it's >=59, make sure archive.py is running the right one:

env CHROME_BINARY=/path/from/step/1/chromium-browser ./archive bookmarks_export.html   # replace the path with the one you got from step 1

Wget & Curl:

If you're missing wget or curl, simply install them using apt or your package manager of choice. See the "Manual Setup" instructions for more details.

If wget times out or randomly fails to download some sites that you have confirmed are online, upgrade wget to the most recent version with brew upgrade wget or apt upgrade wget. There is a bug in versions <=1.19.1_1 that caused wget to fail for perfectly valid sites.

Archiving

No links parsed from export file:

Please open an issue with a description of where you got the export, and preferrably your export file attached (you can redact the links). We'll fix the parser to support your format.

Lots of skipped sites:

If you ran the archiver once, it wont re-download sites subsequent times, it will only download new links. If you haven't already run it, make sure you have a working internet connection and that the parsed URLs look correct. You can check the archive.py output or index.html to see what links it's downloading.

If you're still having issues, try deleting or moving the output/archive folder (back it up first!) and running ./archive again.

Lots of errors:

Make sure you have all the dependencies installed and that you're able to visit the links from your browser normally. Open an issue with a description of the errors if you're still having problems.

Lots of broken links from the index:

Not all sites can be effectively archived with each method, that's why it's best to use a combination of wget, PDFs, and screenshots. If it seems like more than 10-20% of sites in the archive are broken, open an issue with some of the URLs that failed to be archived and I'll investigate.

Removing unwanted links from the index:

If you accidentally added lots of unwanted links into index and they slow down your archiving, you can use the bin/purge script to remove them from your index, which removes everything matching python regexes you pass into it. E.g: bin/purge -r 'amazon\.com' -r 'google\.com'. It would prompt before removing links from index, but for extra safety you might want to back up index.json first (or put in undex version control).

Hosting the Archive

If you're having issues trying to host the archive via nginx, make sure you already have nginx running with SSL. If you don't, google around, there are plenty of tutorials to help get that set up. Open an issue if you have problem with a particular nginx config.

Roadmap

If you feel like contributing a PR, some of these tasks are pretty easy. Feel free to open an issue if you need help getting started in any way!

Major upcoming changes:

change the name
make it a modularized python package to allow installing via pip and importing individual componenets
add a plugin architecture and allow people to contribute plugins for archive methods, indexers, parsers, etc
add a web GUI for managing sources and adding new links

Minor upcoming changes:

download closed-captions text from youtube videos
body text extraction using fathom
auto-tagging based on important extracted words
audio & video archiving with youtube-dl
full-text indexing with elasticsearch/elasticlunr/ag
video closed-caption downloading on Youtube for full-text indexing of video content
automatic text summaries of article with nlp summarization library
featured image extraction
http support (from my https-only domain)
try wgetting dead sites from archive.org (https://github.com/hartator/wayback-machine-downloader)

Changelog

v0.1.0 released
support for browser history exporting added with ./bin/export-browser-history
support for chrome --dump-dom to output full page HTML after JS executes
v0.0.3 released
support for chrome --user-data-dir to archive sites that need logins
fancy individual html & json indexes for each link
smartly append new links to existing index instead of overwriting
v0.0.2 released
proper HTML templating instead of format strings (thanks to https://github.com/bardisty!)
refactored into separate files, wip audio & video archiving
v0.0.1 released
Index links now work without nginx url rewrites, archive can now be hosted on github pages
added setup.sh script & docstrings & help commands
made Chromium the default instead of Google Chrome (yay free software)
added env-variable configuration (thanks to https://github.com/hannah98!)
renamed from Pocket Archive Stream -> Bookmark Archiver
added Netscape-format export support (thanks to https://github.com/ilvar!)
added Pinboard-format export support (thanks to https://github.com/sconeyard!)
front-page of HN, oops! apparently I have users to support now 😁?
added Pocket-format export support
v0.0.0 released: created Pocket Archive Stream 2017/05/05

Donations

This project can really flourish with some more engineering effort, but unless it can support
me financially I'm unlikely to be able to take it to the next level alone. It's already pretty
functional and robust, but it really deserves to be taken to the next level with a few more
talented engineers. If you want to help sponsor this project long-term or just say thanks or suggest changes, contact
me at bookmark-archiver@sweeting.me.

Grants / Donations

tscs37/bookmark-archiver