KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#typescript #ai-agents #developer-tools #claude-code #codex #cli #agent-skills #ai #dsh-plugin #mcp #windows #agent

serverless-graphql-mongodb-lambda

★ 19 Open GitHub ↗

Lambda integration with serverless framework, vscode offline debugging, apollo-server, graphql, mongoose and atlas mongodb

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# serverless-graphql-mongodb-lambda

[![serverless](http://public.serverless.com/badges/v3.svg)](http://www.serverless.com)
[![JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://standardjs.com)
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
[![Commitizen friendly](https://img.shields.io/badge/commitizen-friendly-brightgreen.svg)](http://commitizen.github.io/cz-cli/)
[![semantic-release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg)](https://github.com/semantic-release/)

## Features / Tools

1. VSCode debugger setup at `.vscode/launch.json` with serverless-offline, just press f5 to start a local server and inspect break points
1. Apollo-Server v2 setup for an AWS Lambda
1. Caching GraphQL Responses in memory or redis
1. MongoDB/Mongoose integration & Caching connections outside of lambda handler
1. Serverless setup for different environments & deployment targets
1. serverless-warmup plugin integration to reduce cold starts possibility and keep the lambdas warm
1. Semantic-versioning, changelog generation and automated releases thanks to semantic-release
1. Linting with StandardJS
1. Gzip compression
1. Environment variables per stage can be defined in an `env.yml` file
1. AWS X-Ray integration for traces
1. GraphQL Playground integration w/ traces
1. Apollo Engine/Graph Manager integration for monitoring
1. Serverless Dashboard monitoring

## Setup

- Setup your aws credentials and aws profile using `aws configure --profile <aws profile>`
- `npm install`
- use `yarn start` to run in offline mode`
- `yarn deploy:dev` to deploy dev environment
- `yarn deploy:live` to deploy to live

## Environment variables

- Environment variables can be setup in `env.yml` file
- add your `ENGINE_API_KEY` to a .env file

## Deploying

- Install serverless cli using `npm i -g serverless`
- Install and setup your aws cli with an aws profile using `aws config --profile=<aws profile>`
- use `yarn deploy:dev` or `yarn deploy:live`

## Releasing

This repo uses [semantic-release](https://github.com/semantic-release/semantic-release), [commitizen](https://github.com/commitizen/cz-cli), [commitlint](http://commitlint.js.org), [husky](https://github.com/typicode/husky) and [conventional commits](https://conventionalcommits.org/en/v1.0.0-beta.4/) in order to automate the release proccess

### Setup/Prequisites

1. The user needs to have a `GH_TOKEN` environment variable set with a valid git token that has push access to the repository which can be generated following these [steps](https://help.github.com/en/articles/creating-a-personal-access-token-for-the-command-line)
2. the token can be added into a `~/.bash_profile` to avoid manually setting it before running the command.
3. The script should be run from the release branch only (default: master) otherwise it will fail. To change the release branch you can edit the "release" section in the `package.json` file to temporarily set the release branch as follows
  
```js
"release": {
  ...
  "branch": "feature/integrate-semantic-release"
  ...
}
```

### Usage

- `yarn commit` will run commitizen cli to generate a conventional style commit message
- `yarn release` will do a dry-run of the release without pushing or changing any files
- `yarn release --no-ci` will do a real release.
We could potentially use this to automate releases when new commits/PRs land in the master branch
Details

### A release will

- Bump the version in `package.json` according to semantic versioning (semver) based on the changes/commit messages (fix/perf = patch, feat = minor, breaking = major)
- Create a git tag
- Generate a CHANGELOG.md with the latest changes since the last release
- Push the changes to the repository & create a git release

serverless-graphql-mongodb-lambda

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README