A GraphQL API wrapper for The Movie DB built with Apollo Data Sources.
Note: v3 is currently under development, meaning these docs are subject to change!
Install dependencies by running
yarn, then create a new file in the root directory named
.env. You'll need to get an API key from The Movie DB in order to run any queries. For more information, please read the Movie DB docs. Additionally, if you want to track usage metrics for your API, you'll need to get an API key from Apollo Graph Manager. For instructions on how to do that, please read the Apollo Graph Manager docs. In your new
.env file, copy + paste the following and replace the text following the
= sign with your newly create API keys.
MOVIE_DB_API_V3_KEY=<insert your movie database v3 api key here>
MOVIE_DB_API_V4_KEY=<insert your movie database v4 api key here>
APOLLO_KEY=<insert your apollo studio api key here>
Once that's done, you can now start up a development server using
yarn start. By default this will use Serverless Offline, but if you would instead like to use Netlify Lamba, you can run
yarn start:netlify instead. Once the development server is listening, you can pull up a GraphQL Playground by visiting one of the following URLs:
You can try out the API using the GraphQL Playground hosted at https://tmdb-api.saeris.io/.netlify/functions/tmdb-api
Testing is provided via
jest and is pre-configured to run with
codecov as well. While tests for this project are far from complete, they can be found under
src/__TEST__ and follow a naming format of
[filename].spec.ts. Additionally, this project uses
prettier, all three of which are automatically run on each commit via
lint-staged. To manually lint and test, use the following commands:
Test and watch for changes:
Lint + Typecheck + Test:
To deploy the server, you'll need to follow the Serverless Framework's Setup Guide to deploy to AWS. If you'd rather use Netlify, you'll need to follow whichever method works best for your workflow. Refer to Netlify's Docs for more information.
If you're deploying to AWS, you can use the following commands to deploy to Staging or Production:
Alternatively, if you're using Travis CI, you can deploy to both on each commit as part of your CI process by uncommenting the following lines inside
# deploy develop to the staging environment
- provider: script
script: yarn deploy:dev
# deploy master to production
- provider: script
- yarn deploy:prod
Released under the MIT license.