🚀 A drop-in replacement for the Mercury Parser API.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci chore: setup some linting+tests for greenkeeper Feb 7, 2019
.github initial commit Feb 6, 2019
fixtures initial commit Feb 6, 2019
src deps: update for 2.0 mercury parser Feb 16, 2019
.babelrc initial commit Feb 6, 2019
.eslintignore
.eslintrc initial commit Feb 6, 2019
.gitignore initial commit Feb 6, 2019
.npmignore initial commit Feb 6, 2019
.nvmrc initial commit Feb 6, 2019
.prettierrc initial commit Feb 6, 2019
LICENSE-APACHE initial commit Feb 6, 2019
LICENSE-MIT initial commit Feb 6, 2019
README.md docs: update README with AWS cli setup link Feb 13, 2019
jest.config.js initial commit Feb 6, 2019
package.json chore(package): update ts-jest to version 24.0.0 Feb 18, 2019
serverless.yml
tsconfig.json initial commit Feb 6, 2019
tslint.json initial commit Feb 6, 2019
webpack.config.js initial commit Feb 6, 2019
yarn.lock chore(package): update lockfile yarn.lock Feb 18, 2019

README.md

Mercury Parser API

Greenkeeper badge

This repo provides a drop-in replacement for the Mercury Parser API. In fact, this AWS Lambda-based API for running the Mercury Parser is the same code and serverless infrastructure that powered the Mercury Parser API.

Installation

# If you don't already have the mercury parser api installed, do that
git clone https://github.com/postlight/mercury-parser-api.git

# Install dependencies
yarn install

API Gateway-like local dev server

To spin up a local dev server that will more closely match the API Gateway endpoint/experience:

yarn serve

Deploy

Assuming you've already set up your default AWS credentials (or have set a different AWS profile via the profile field), simply run:

yarn deploy

yarn deploy will deploy to "dev" environment. You can deploy to stage or prod with:

yarn deploy:stage

# -- or --

yarn deploy:prod

After you've deployed, the output of the deploy script will give you the API endpoint for your deployed function(s), so you should be able to test the deployed API via that URL.

License

Licensed under either of the below, at your preference:

Contribution

Unless it is explicitly stated otherwise, any contribution intentionally submitted for inclusion in the work, as defined in the Apache-2.0 license, shall be dual licensed as above without any additional terms or conditions.