feat: docker files

[seeratawan01]

PR Type

enhancement, configuration changes

---

Description

• Added Docker-related configuration files for the JavaScript SDK package.
• Implemented a .dockerignore file to exclude node_modules from Docker builds.
• Introduced a docker-compose.yaml file to define service configuration and port mapping.
• Created a multi-stage Dockerfile for building with Node.js and serving with Nginx.
• Configured Nginx with a default server and main configuration files, including gzip compression and logging.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	.dockerignore Add .dockerignore to exclude node_modules                                packages/javascript-sdk/.dockerignore - Added `.dockerignore` file to exclude `node_modules` directory. +1/-0      docker-compose.yaml Add docker-compose configuration for server service            packages/javascript-sdk/docker-compose.yaml Added docker-compose.yaml for service configuration. Configured service server with container name usermaven-tracker. Mapped port 9000 to 80. +10/-0    default.conf Add default Nginx server configuration                                      packages/javascript-sdk/docker/default.conf Added Nginx server configuration for default settings. Configured content expiration and error pages. +34/-0    nginx.conf Add main Nginx configuration with gzip and logging              packages/javascript-sdk/docker/nginx.conf Added Nginx main configuration file. Configured logging, gzip compression, and included conf.d files. +58/-0
Enhancement	Dockerfile Create multi-stage Dockerfile for Node.js and Nginx            packages/javascript-sdk/docker/Dockerfile Created multi-stage Dockerfile for building and serving with Nginx. Used Node.js for building and Nginx for serving. Configured file copying and Nginx setup. +10/-0

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[github-actions[bot]]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🏅 Score: 85

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Possible Bug The Dockerfile uses 'pnpm' for package management, which might not be installed in the base image, potentially causing the build to fail. Security Concern Using 'nginx:latest' as a base image may introduce vulnerabilities through uncontrolled updates. It's safer to use a specific version.

Code feedback:

---

relevant file	packages/javascript-sdk/docker/Dockerfile
suggestion	Consider using a specific version of the Node.js image instead of '16.5.0-alpine' to ensure compatibility and stability across different environments. [important]
relevant line	FROM node:16.5.0-alpine AS builder

---

relevant file	packages/javascript-sdk/docker/Dockerfile
suggestion	Add error handling for the 'COPY' command to ensure files are copied successfully, especially when dealing with external build contexts. [medium]
relevant line	COPY . .

---

relevant file	packages/javascript-sdk/docker/nginx.conf
suggestion	Consider disabling 'gzip' for security reasons, as it can be exploited via BREACH attacks if HTTPS is not configured properly. [medium]
relevant line	gzip on;

---

[github-actions[bot]]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Best practice	Ensure consistent Docker builds by using a specific Nginx version ___ **Replace the use of nginx:latest with a specific version of Nginx to ensure consistent, predictable builds and avoid potential incompatibilities with future versions.** [packages/javascript-sdk/docker/Dockerfile [6]](https://github.com/usermaven/usermaven-js/pull/103/files#diff-7a5f39cf5bcb819885a0b5b04234de54a0201b2149e76ad9bf4584839d6cba4eR6-R6) ```diff -FROM nginx:latest +FROM nginx:1.21.6 ``` Suggestion importance[1-10]: 8 Why: Using a specific version of Nginx ensures consistent and predictable builds, reducing the risk of incompatibilities with future versions. This is a best practice for Docker images.	8
Performance	Simplify the build process by using npm, which is pre-installed in the Node Docker image ___ **Consider using a package manager that is already available in the Node Docker image, such as npm or yarn, instead of installing pnpm, to reduce build times and complexity.** [packages/javascript-sdk/docker/Dockerfile [4]](https://github.com/usermaven/usermaven-js/pull/103/files#diff-7a5f39cf5bcb819885a0b5b04234de54a0201b2149e76ad9bf4584839d6cba4eR4-R4) ```diff -RUN pnpm install && pnpm build +RUN npm install && npm run build ``` Suggestion importance[1-10]: 7 Why: Using npm, which is pre-installed, can reduce build times and complexity by avoiding the need to install an additional package manager like pnpm. This suggestion improves performance and simplifies the Dockerfile.	7
Maintainability	Simplify Dockerfile and reduce image layers by directly overwriting Nginx configuration files ___ **Avoid using RUN rm to remove default Nginx configuration files; instead, overwrite them directly in the Dockerfile to simplify the Dockerfile and reduce layers.** [packages/javascript-sdk/docker/Dockerfile [8-10]](https://github.com/usermaven/usermaven-js/pull/103/files#diff-7a5f39cf5bcb819885a0b5b04234de54a0201b2149e76ad9bf4584839d6cba4eR8-R10) ```diff -RUN rm /etc/nginx/nginx.conf && rm /etc/nginx/conf.d/default.conf +COPY docker/nginx.conf /etc/nginx/nginx.conf +COPY docker/default.conf /etc/nginx/conf.d/default.conf ``` Suggestion importance[1-10]: 6 Why: Directly overwriting configuration files instead of removing them first can simplify the Dockerfile and reduce the number of layers in the image, enhancing maintainability.	6