Skip to content

Commit

Permalink
chore: Dockerize backend
Browse files Browse the repository at this point in the history
  • Loading branch information
gabrielmachin committed Dec 20, 2023
1 parent c14178f commit ec01d9d
Show file tree
Hide file tree
Showing 9 changed files with 848 additions and 7,912 deletions.
5 changes: 3 additions & 2 deletions Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,11 @@ WORKDIR /home/node/app
# Copy dependency information and install production dependencies
COPY *.json ./

RUN npm install --production --pure-lockfile --ignore-scripts
RUN npm ci --omit=dev --ignore-scripts
RUN cp -RL node_modules/ /tmp/node_modules/

# Install all dependencies
RUN npm install --pure-lockfile --ignore-scripts
RUN npm ci --ignore-scripts

# Copy source code (and all other relevant files)
COPY . .
Expand All @@ -34,6 +34,7 @@ COPY --from=builder /home/node/app/prisma ./prisma
# Copy runtime project
COPY --from=builder /home/node/app/dist ./dist
COPY --from=builder /home/node/app/package*.json ./
COPY --from=builder /home/node/app/tsconfig.json ./

EXPOSE 8080

Expand Down
16 changes: 16 additions & 0 deletions Dockerfile.dev
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
# Start with fully-featured Node.js base image
FROM node:20.9.0 AS builder
WORKDIR /home/node/app

# Copy dependency information and install dependencies
COPY *.json ./

RUN npm ci --ignore-scripts

# Copy source code (and all other relevant files)
COPY . .

# Generate Prisma Client
RUN npx prisma generate

CMD [ "npm", "run", "dockercmd" ]
15 changes: 12 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,12 +34,21 @@ npm test

## Project Setup

There are currently two ways in which we can make the setup of the project, one would be running the whole setup with docker, and the other running everything but the backend project with docker.

### Running the whole setup with docker
You only need to install [Docker](https://docs.docker.com/engine/install/) and [Docker Compose](https://docs.docker.com/compose/install/). To start the containers, run `docker-compose up`, and the -d flag if you want to run it in detached mode.
Once the containers are running, you can go to `http://localhost:8080/docs` to see the API documentation.
If you want to interact with the project container terminal you can run the command `docker-compose exec backend bash` and then run e.g `npm run test`


### Running only the db and Redis with docker
* Install Node 20.9.0 (as documented on [`.node-version`](./.node-version))
* Install the appropriate version of npm: `npm i -g [email protected]`
* Install packages with `npm install`
* Create a new `.env` file using the `.env.example` as an example. for that run `$ cp .env.example .env`.
* Set the variables in the new environment file `.env` you created above.
* Start the redis container with `docker-compose up redis-server`
* Start the db and redis container with `docker-compose up db redis-server`
* Start the project with `npm start`

## Project structure
Expand All @@ -65,7 +74,7 @@ npm test
[Prisma](https://www.prisma.io/docs/concepts/overview/what-is-prisma) is a next-generation ORM for Node.js.
`prisma client` - Auto-generated and type-safe query builder for Node.js & TypeScript.
`prisma migrate` - Prisma migration system.
Requeriments:
Requirements:
* set a `DATABASE_URL` on .env - The format is specified in .env.example
* Running database: There's a docker-compose file example: `docker-compose up -d`
* Run database migrations: `npx prisma migrate dev`
Expand All @@ -90,7 +99,7 @@ TSOA uses decorators to define the API routes and docs. check out the [TSOA docs

## Docker Configuration
A [`Dockerfile`](./Dockerfile) has been added to this project. The main reason to use Docker is to generate a production build, it is not intended for use for development.
In fact, the Dockerfile has instructions only for generating the production-ready build. This is a multi-stage build that will build the project, run the migrations, and then run the server only with production dependiencies.
In fact, the Dockerfile has instructions only for generating the production-ready build. This is a multi-stage build that will build the project, run the migrations, and then run the server only with production dependencies.

### BullMQ worker
* To add a new worker we just need to create a `new Worker()` object in the worker folder and pass a queue name to pick up tasks from.
Expand Down
14 changes: 14 additions & 0 deletions docker-compose.yml
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,20 @@ services:
POSTGRES_DB: 'nodeTemplateDBTesting'
ports:
- '5433:5432'
backend:
build:
dockerfile: Dockerfile.dev
env_file:
- .env
depends_on:
- db
- redis-server
volumes:
- .:/home/node/app
ports:
- '8080:8080'
stdin_open: true
tty: true
volumes:
db:
redis-data:
Loading

0 comments on commit ec01d9d

Please sign in to comment.