Replacing Postlight’s Mercury scraping service with your self-hosted copy

Mercury by Postlight is a tool for scraping web pages. It “transforms web pages into clean text. Publishers and programmers use it to make the web make sense, and readers use it to read any web article comfortably.”
This was a fast, free web-based service, accessible via an API which worked rather beautifully, without a fuss.

Then, in February 2019, Postlight announced they were discontinuing the hosted service and open-sourcing the code. A mixed blessing, as, to keep using the service, this now required users of the service to set up their own version of Mercury, on their own, or Amazon’s servers.
Some guidance was provided, but few of those posting in the discussion group were (easily?) able to resolve the issues surrounding setting up their own instance. For me, Mercury using technology I’m not very familiar with, this was a bit of a hit-and-miss process that, eventually, did pay off.

Stephen Bradley wrote up a guide on how to get Mercury running on an Amazon server, but I like to stay clear from Amazon.

Here’s what I did to get Mercury running on my own server. Your mileage may vary.

  1. I’m using DreamHost. When setting up a (sub-)domain, I can select the option ‘Passenger’, which is for running Ruby, NodeJS and Python apps.
  2. SSH to the new domain and install NVM as described here. 
    curl -o- | bash
  3. After running that script, a message claims that you only have to close and open the terminal to have nvm running. That did not work for me and I had to run this (in the terminal):
    export NVM_DIR="$HOME/.nvm"
    [ -s "$NVM_DIR/" ] && \. "$NVM_DIR/" # This loads nvm
    [ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion" # This loads nvm bash_completion
  4. Update nvm to the minimum required version, in the terminal (based on this post):
    nvm install 8.10
  5. This did not result in the installed version of node sticking between sessions. I had to edit my bash profile and add a line to it.
    To edit my bash profile:
    nano ~/.bash_profile
    Adding the following line:
    source ~/.bashrc
  6. Install the mercury parser in the terminal (based on this):
    npm install @postlight/mercury-parser
  7. Create a javascript file, for example with:
    const Mercury = require('@postlight/mercury-parser');
    const url = '';
    Mercury.parse(url).then(result => { console.log(result); } );
  8. Execute the file from the command line with:
    node myfile.js
    But, this does not make the result available through the web.
  9. Install expressjs as detailed here.
  10. Create /myapp/app.js with this:
    const express = require('express')
    const app = express()
    const port = 8888

    app.get('/myapp/', function (req, res) {
    const Mercury = require('@postlight/mercury-parser');
    const url = req.query.url;
    Mercury.parse(url).then(result => {
 } );

  11. Run the app from the command line:
    node app.js
  12. Visit the page in the browser:
  13. But, you want this app to run forever. Install forever:
    npm install forever -g
  14. Start forever:
    forever start app.js

Now, I can replace this:

Related:  Let the sun shine

$postlightUrl = "".$url;

With this:

$postlightUrl = "".$url;

Somewhat broken

This worked, but, a few weeks later, it no longer did. The version of node, nvm, did not persist between sessions. This was resolved by adding what is now step 5, above.

I also threw together a quick PHP-based solution that essentially does the same as the Mercury parser: extracting basic details from a webpage.