docker-compose.dev.yml. If you are using those services as part of an integration or end-to-end tests you need to provide a file named
docker-compose.ci.yml. Optionally if you need to share service setup between local dev and CI run you can do so by extracting the common parts in a file named
runServermethod of the
infra-nest-serverto run your Nest.js server. It is pre-configured with everything needed for telemetry and security. All you need is to provide your main app module as per the example.
logginglibrary and not
console.log. Even better, use Nest.JS dependency injection to inject a logging instance, which can be overridden and spied in tests.
logginglibrary provides a single place to control the log routing so if you deviate from that you might not have your log statements delivered correctly to our central storage.
infra-nest-serverit is already configured to collect metrics for all your routes and export metrics to be scraped.
infra-nest-serverit is already configured to provide support for tracing for HTTP/HTTPS API calls as well as support for your service to participate in tracing. We have not added support for tracing to Postgres as is but hope to take care of this soon enough. You do not need to do anything for this to work. It will start working automatically when we add this.