To initiate the project, please submit a project creation request to the administrator via the provided form. Upon approval, the administrator will grant access to a Git repository hosted on GitHub. Authorized users will then have the capability to create branches within this repository, facilitating collaborative development and version control.
Remember: the 'main' branch cannot be modified directly, each developer need to use branches and create a github Pull Request(PR) to merge desidere branches into main |
The cloned repository will have a structure like this:
This document provides a detailed description of the organizational structure of the project, including directories and files, along with their respective purposes:
.github/workflow
: This directory contains the GitHub workflow configurations that are integrally linked to the 'deployment project', as established by the project administrator in conjunction with the development project. These workflows are critical for automating and managing the project's deployment processes.
src
: The src
directory serves as the repository for the project's source code. It includes a demonstration index.js
file, which is designed to output the "Hello World" string in response to each request made to the root URI (/
). This directory is essential for housing the core logic and functionality of the application.
test
: This directory is dedicated to housing the project's test files. It includes tests specifically for the index.js
file located within the src
directory, ensuring the reliability and correctness of the application's main functionality.
Dockerfile
: This file provides a predefined Dockerfile that serves as an exemplary starting point for developers. It is crafted to facilitate the containerization of the application, enabling consistent deployment and runtime environments. this file is principally used by the predefined github workflow that use it to build the docker image that will be deployed on EED kubernetes cluster.
LICENSE.md
: This file contains the standard SLAC (Software License Agreement for Collaboration) license, which governs the use and distribution of the project's software. It is crucial for defining the legal framework under which the project operates.
package.json
and package-lock.json
: These files are standard to Node.js projects and contain the initial library dependencies required to create the demo. They play a vital role in managing the project's dependencies and ensuring consistent environments across different setups.
The |
README.md
: As the primary documentation file for the application, the README.md
is pre-configured with the standard SLAC logo and is intended to be filled with comprehensive information about the project, including its purpose, setup instructions, and usage guidelines.
Each component of the project's structure is designed to support its development, deployment, and documentation, ensuring a streamlined workflow for contributors.
here we are going to give an overview of the file that has been created for the startup project:
const express = require("express"); const app = express(); const port = 3000; app.get("/", (req, res) => { res.send("Hello World!"); }); const server = app.listen(port, () => { console.log(`Example app listening at http://localhost:${port}`); }); module.exports = { app, server }; // Export both app and server |
This file is a demo that uses the express framework to create route that can be accessible via HTTP
To build upon this demo, consider adding more routes, middleware for handling various HTTP methods, static files, or even integrating with a database. Express makes it easy to scale applications from simple demos to full-featured web applications.
This demo application provides a basic introduction to creating web servers with Node.js and Express. By understanding how to set up a simple server and respond to HTTP requests, you can begin to explore more complex applications and APIs using Express.
The application exports both the app
and server
objects, allowing for easy integration and testing within larger applications or microservices. This practice is beneficial for unit testing or when importing the application as a module in other parts of a project.
Probably the NodeJS backend in development would need to talk with other service like database, s3 storage or others. For this reason use docker to help bringing up a development environment. Create a docker-compose.yaml file with all the needed service, ad example to integrate a PostgreSQL database could be used this docker-compose.yml file content:
version: '3.8' services: db: image: postgres:latest environment: POSTGRES_DB: demodb POSTGRES_USER: demo_user POSTGRES_PASSWORD: demo_pass volumes: - ./init-db:/docker-entrypoint-initdb.d # Mount the directory containing demo_schema.sql ports: - "5432:5432" restart: unless-stopped |
demo_schema.sql is a file contained into the init-db folder that can contains somenitng like:
-- Create a simple table named 'demo_table' CREATE TABLE demo_table ( id SERIAL PRIMARY KEY, name VARCHAR(255) NOT NULL, email VARCHAR(255) UNIQUE NOT NULL, created_at TIMESTAMP WITH TIME ZONE DEFAULT CURRENT_TIMESTAMP ); |
to startup the docker compose service run the following command:
docker-compose up -d |
at this point the PostgreSQL service is accessible from the localhost:5432 tcp address. To create more comples docker-compose file read the official documentation.
const { server } = require("../src/index"); // Adjust the path as necessary const request = require("supertest"); describe("index.js", function () { after(function () { server.close(); // Close the server after tests }); it("Test echo root path", function (done) { request(server).get("/").expect(200, done); }); }); |
The test uses supertest
, a popular testing library for HTTP assertions, allowing us to test the response of our Express application without starting the server manually. This file contains a single test suite that verifies the server's response to a GET request at the root URL.
index.js
file, this is the Express application server we're testing./
) and expects a 200 OK response. If the server responds as expected, the test passes. The done
callback is used to handle asynchronous testing, ensuring that the test waits for the server's response before completing.With the preparatory steps completed, you are now ready to embark on the development of your application. To ensure a smooth and efficient workflow, it is recommended to adhere to the following guidelines:
Branch Creation:
feature/
, fix/
, or improvement/
to provide clear context. The name of the branch will be incorporated into the PR (Pull Request) merge message and will be recorded in the source code history.Commit and Push:
Testing:
Pull Request and Merge:
The execution of a merge workflow upon PR creation or modification, which includes running all tests located in the test folder. Should any issues arise, the PR will be blocked until these are resolved. This workflow acts as a critical checkpoint.
Check the log for each github action job in case of errors |
Deployment Workflow:
Following these steps not only ensures a systematic approach to application development but also fosters a culture of testing and continuous integration, thereby enhancing the quality and reliability of your application. Upon completion, the cycle can recommence with the creation of a new branch for additional features, returning to the beginning of this guide.
|