Initial setup

[magley]

This is the initial setup of the user microservice.

It includes dockerization, connecting to PostgreSQL and a simple workflow that tests the app and builds it. It doesn't deploy to DockerHub because I didn't bother setting up semantic versioning and all that stuff.

Build and run using docker compose.
To test the server, run curl http://localhost:8080/ping from a different terminal. It should return "Pong!".

You can also do automatic testing via run-tests.sh which is a stub for now. You need bash to test it (so Linux or Git Bash or WSL (not recommended because of line ending differences, I couldn't get it to work)). I could add a Powershell script too, but the CI/CD workflow will only use .sh.

Things I have added:

• multi-stage build
• dockerfile caching
• github action dependency caching

Things I haven't added:

• publishing to DockerHub (already mentioned above)
• support for integration tests (too early to decide what we're going to do about this)
• tracing, logging and monitoring
• advanced code analysis (we only need to do this for one microservice, but still)
• test coverage report atrifacts (do we need this?)

Also, apparently, the paths: field in github actions workflows checks for the entire PR, and not just the commit. That's why b8bca1e triggered the Actions to run even if it changed only a .md which doesn't match paths:

[Vasilijez]

You established a nice initial setup.

Regarding "test coverage report artifacts (do we need this?)", I guess we should check with the assistant. I'm ready to send him a message about it.

[Vasilijez]

I only have read access, which is why my review approval didn’t count.