ducphd2 / dbildungs-iam-server

dBildungs IAM Server

We have the strategic goal SG-02 "stand-alone system". We want to succeed this goal, therefor we need to set the ErWIn system separate to the dBC. This repository is used for the development the separate ErWIn system to achieve this goal.

Prerequisites

• Node in the version stated in the package.json
• Container Runtime like Docker or Podman
  • Is required for local setup and integration tests

Local Setup

1. Run npm ci to install all dependencies
2. Start the required services from the compose.yaml file
   • db
3. Create a .env file and set the required environment variables from env.config.ts
4. run npm run setup to initialize the DB
5. Run npm run start:debug to start the server
6. Server runs on the url printed in the console

Scripts for Development

Command	Description	Hint
Setup
npm ci	Installs all required dependencies
Build
npm run build	Compiles all *.ts files
Run
npm run start	Starts the server	No debug port
npm run start:debug	Starts the server in debug mode	Debug port is open
npm run start:prod	Starts the server in production mode
Test
npm run test:cov	Runs all tests with coverage	Success is a merge requirement
npm run test:unit	Runs only unit tests	Files with *.spec.ts ending
npm run test:integration	Runs only integration tests	Files with *.integration-spec.ts ending
npm run test:watch	Starts the interactive watch mode
Lint
npm run format	Runs the formatter
npm run lint	Runs the linter	Success is a merge requirement
npm run lint:fix	Runs the linter and fixes auto fixable problems
Backend for Frontend
npm run start:frontend	Starts the backend for frontend server	No debug port
npm run start:frontend:debug	Starts the backend for frontend server in debug mode	Debug port is open
npm run start:frontend:prod	Starts the backend for frontend server in production mode
Console Applications
npm run setup	Runs db:init to Initialize the DB
npm run db:init	Initializes the database (applies SQL schema)	compose.yaml can be used

Developer Guides

• Code conventions are enforced through the compile, eslint and prettier as far as possible
  • Non enforcable conventions will be documented here. If they become enforcable we will put them into automation.
  • Table names will be all lowercase if the name contains multiple words they will be separated by underscores.
• Git conventions can be found here
• Test conventions can be found here
• Configuration conventions can be found here

License

The software is licensed under the AGPL-3.0 license.