Skip to content

Latest commit

 

History

History
201 lines (140 loc) · 8.16 KB

configuration.md

File metadata and controls

201 lines (140 loc) · 8.16 KB
Raw

LACChain Trust

This project includes the boilerplate for a basic rest-api made in Node.JS with Express + Typescript.

Basic Requirements

  1. Install Node.js (lts-version v16.20.0)
  2. Install yarn if not present curl -o- -L https://yarnpkg.com/install.sh | bash (macOS and generic Unix environments)
  3. Install required dependencies by yarn
  4. cp .example.env .env.dev
  5. cp .example.env .env.prod
  6. cp .example.env.test .env.test
  7. Create your DB (i.e. psql for Postgres: psql -U <user> -h <host> -c "create database <db name>;") with same name as your .env file.
  8. Run ENV=[dev, test, prod] yarn db:setup.
  9. Start your server with ENV=[dev, prod] yarn dev.

Some scripts

Add ENV=[dev, prod] before running scripts. Why?: Configuration file used by Typeorm

Run yarn build to build js from typescript source.

Run yarn start to start the server from the compiled folder (/dist).

Run yarn test to run tests.

Run yarn dev to start and automatically detect any source-code changes, restarting the server as well.

Run yarn typeorm schema:drop to drop your schema of the DB.

Run yarn typeorm schema:sync to resync the schema of your DB.

Run yarn seed:run to run seed files.

Run yarn db:reset to drop schema and re run it, then seed the DB.

Run yarn typeorm migration:generate -n <migration's name> to create a new migration.

Run yarn typeorm migration:run to run pending migrations.

Run yarn typeorm migration:revert to rollback migrations.

Run yarn typeorm migration:show to see the list of all migrations (pending and also ran).

Github Actions

Our CI workflow is based on Github Actions, for this, we need to set several secret keys for integrated with some services like SonarQube or databases for example. To configure these keys in the GitHub repo, you can follow the next guideline. Also, for configuring the SonarQube keys you can follow the next steps.

Action Secret Key
Password for the database that is used in the testing step TEST_POSTGRES_PASSWORD
URL of SonarQube server SONAR_URL
Key of the project on the SonarQube server SONAR_PROJECT_KEY
Token generated of the project in the SonarQube server SONAR_TOKEN

Running with Docker

Prerequisites

In order to run the app with Docker, you should install or update to the latest version, we recommend to install Docker-Desktop due to composer and some cool CLI-UI tools are included.

Development with Docker

The following commands will build and run all you need to start working on the base, without any other installation requirements. Important: if you already have postgres running locally, you'll need to kill the service before run docker-compose up.

docker network create backend

docker-compose -f docker-compose-dev.yml --env-file .env.dev build

docker-compose -f docker-compose-dev.yml --env-file .env.dev up

Testing Docker production images with docker-compose

The following commands will build and run all you need to start working on the base, without any other installation requirements. Important: if you already have postgres running locally, you'll need to kill the service before run docker-compose up.

docker network create backend

mkdir pg-prod-db

docker-compose -f docker-compose.yml --env-file .env.prod build

docker-compose -f docker-compose.yml --env-file .env.prod up

Deployment with Docker (only for production)

The following commands will build and run a Docker image ready for production and size-optimized.

Build Docker image

docker build -f Dockerfile.prod -t lacchain-trust .

Run docker image (you need to add .env file as param)

docker run --rm --env-file=.env.prod -p 3000:3000 --name node-api lacchain-trust

Fix issue at build docker image (dependencies to install bcrypt are not providede in alpine version of node)

Add the following line before the command RUN yarn in the Dockerfile.

RUN apk --no-cache add --virtual builds-deps build-base python

Debugging

If you're using VSCode, you can run the API in debug mode by clicking on Debug > Start Debugging or with the shortcut F5. This will start the app in DEV mode and then you can add as many breakpoints as you need.

API Documentation

After running the server you will find OpenAPI Specification here: http://<host>:<port>/docs

App scaffolding

This is the suggested scaffolding for this project. You can take a look at:

.
├── __tests__
│   └── ...
├── src
│   ├── config
│   │   └── ...
│   ├── controllers
│   │   └── ...
│   ├── database
│   │   └── ...
│   ├── entities
│   │   └── ...
│   ├── interfaces
│   │   └── ...
│   ├── services
│   │   └── ...
│   ├── utils
│   │   └── ...
│   ├── views
│   │   └── ...
│   ├── app.ts            (App root and is where the application will be configured.)
│   ├── server.ts         (HTTP server)
├── README.md
├── .nvmrc                (Locks down your Node version.)
├── jest.config.js        (Jest configuration file.)
├── yarn-lock.json
├── package.json          (Your application’s package manifest.)
├── tsconfig.json         (The TypeScript project configuration.)
├── prod-path.js          (Tool used to run in production, translates ts-path and alias)

Dependencies

  • routing-controllers - Create structured class-based controllers with decorators usage in Express.
  • routing-controllers-openapi - Runtime OpenAPI v3 schema generation for routing-controllers.
  • swagger-ui-express - Serves auto-generated swagger-ui API docs from express.
  • typeorm - NodeJS ORM.
  • nodemon - Utility that will monitor for any changes in your source and automatically restart your server.
  • multer - NodeJS middleware for handling multipart/form-data.
  • tsconfig-paths - Utility to register relative paths set at tsconfig file
  • express-rate-limit - Basic rate-limiting middleware used to limit repeated requests to public APIs
  • morgan - HTTP request logger middleware for node.js
  • nodemailer - Module for Node.js to allow the easy email sending.

Code Quality

This repo is integrated with SonarQube for static code analysis and test coverage reporting. This guide covers all the steps, including how to run the test coverage on a local machine. Use the provided sonar-project.properties as-is. Once that is covered:

  1. Run yarn test:cover to run tests with coverage reporting.
  2. Run sonar-scanner to import the test results into the sonar dashboard.

Docs

Express documentation Typescript documentation

Credits

Express API Base is maintained by Rootstrap with the help of our contributors.