Feature/27 implement cicd

[viktorpekhun]

Summary

• Add GitHub Actions workflows: PR validation (API + client) and release to production (build, push to Docker Hub, deploy to Azure)
• Add Dockerfiles for API and Angular client with multi-stage builds
• Add Docker Compose for running the full stack locally (API, client, SQL Server)
• Add runtime configuration for Angular — ConfigService loads config.json at startup, injected via envsubst in Docker so API URL is environment-driven without rebuilding
• Add .nvmrc pinning Node 24 LTS; document setup with fnm or direct install in README
• Add Swagger UI for API (Development only)
• Update README with Docker Compose quickstart and local dev instructions for both API and client

WARNING

Now we use Node 24 LTS, so make sure it is installed on your system before runing locally. You can either set it default for this project, or follow steps in README

[eevatsen]

Missing Client-Side Tests: In pr-validation.yml, the build-and-test-client job installs dependencies and builds the project, but it never runs npm test. Regressions in UI logic will not be caught during PR reviews.

[viktorpekhun]

done

[eevatsen]

The release-to-prod.yml workflow builds and deploys immediately upon a push to main. It does not run any unit or integration tests. If a merge to main introduces an integration issue not caught in the PR, it will be deployed directly to production.

[viktorpekhun]

done

[eevatsen]

There are no steps for linting or formatting validation (e.g., dotnet format --verify-no-changes or npm run lint). This allows inconsistent code styles to enter the codebase.

[eevatsen]

The release workflow considers a deployment successful as soon as Azure accepts the image. It doesn't verify if the app is actually "Alive" (e.g., by hitting a /health or /api/status endpoint).

[eevatsen]

In pr-validation.yml, the job runs npm run build and then immediately runs docker build. Since the Dockerfile also performs a build, you are effectively building the Angular app twice, which significantly increases CI time.

[viktorpekhun]

fixed

[viktorpekhun]

There are no steps for linting or formatting validation (e.g., dotnet format --verify-no-changes or npm run lint). This allows inconsistent code styles to enter the codebase.

Didn't add this on purpose. I'm not sure whether code is consistent now, so to avoid delays before demo I decided not to add it

[eevatsen]

Unlike the release workflow, the PR validation workflow does not use cache-from: type=gha. This means every PR build starts from scratch, wasting time on downloading base layers and re-installing packages.

[eevatsen]

nice!