add docker & api route

[wvl94]

💡 PR Summary generated by FirstMate

Overview: Added Docker support and a new API route for enhanced functionality.

Changes:
Dockerfile creation:

• Added a Dockerfile to containerize the application using Node.js 19-alpine.
• Configured environment variables and user permissions for better security.

API route updates:

• Introduced a new GET route /get/:id in exampleRouter.js for fetching data by ID.
• Maintained existing route functionality with permission middleware.

Configuration change:

• Updated default server port in appConfig.js from 8080 to 80 for consistency.

TLDR: This PR adds Docker support, a new API route for data retrieval, and updates the default server port. Review the Dockerfile and new route in exampleRouter.js.

_{^{Generated by FirstMate and automatically updated on every commit.}}

[firstmatebot]

PR Review

⚠️ It seems that you can still improve the quality of your PR:

    ❌ Documentation drift: Update documentation for port change from 80 to 8080.
    ❌ Security issues: Missing permission middleware on '/get/:id' route.
    ❌ Dockerfile optimization: Implement multi-stage builds in Dockerfile.
    ❌ Configuration management: Add server port env variable to helm chart values.yaml.

_{^{Generated by Firstmate to make sure you can focus on coding new features.}}

[firstmatebot]

You changed the application to run on port 8080 in the Dockerfile, while the configuration in appConfig.js now defaults to port 80. This change seems important, so it might be smart to change the documentation accordingly.

For example, update the documentation to reflect the following:

## Running the Application

To start the application, use the following command:

```bash
docker run -p 8080:8080 your-image-name

By default, the application will run on port 80 unless specified otherwise.

[firstmatebot]

The route '/get/:id' is missing the grantAccessByPermissionMiddleware, which is essential for proper permission checks. Update the route definition to include this middleware as follows:

+ router.route("/get/:id").get(grantAccessByPermissionMiddleware([API_PERMISSIONS.PUBLIC_ENDPOINT]), exampleController.getById)

This ensures that access permissions are validated before executing the controller logic.

(Based on guideline 'Routes should check permissions')

[firstmatebot]

Consider using multi-stage builds in your Dockerfile to optimize the build process and reduce the final image size. You can achieve this by separating the build and runtime stages like this:

FROM node:19-alpine AS build
WORKDIR /usr/src/app
COPY package*.json ./
RUN npm install
COPY . .

FROM node:19-alpine
WORKDIR /usr/src/app
COPY --from=build /usr/src/app ./
EXPOSE 8080
CMD ["npm", "start", "--no-update-notifier"]

(Based on guideline 'Dockerfiles should use multi-stage builds')

[firstmatebot]

Ensure that the updated server port environment variable is added to the helm chart values.yaml file under the configmap section for non-secret variables. This will allow for better configuration management and flexibility in your deployments. Here's an example of how you can add it:

configmap:
  serverPort: {{ .Values.serverPort | default "80" }}

(Based on guideline 'Env vars in helm chart values.yaml')