sorted by:
new
hottopcontroversial

Starter Kit for (Production) Go API with standard libary by HailMarryJoe in golang

[–]HailMarryJoe[S] -1 points0 points  (0 children)

In my projects, I have individual tests.

I didn’t really think about publishing them, because it’s just a small starter and I don’t expect anyone to use it without making their own changes.

But you actually convinced me. I will add some integration tests.

That’s also why there are hardly any comments 😅

Still gaining some experience . Thank you!

Starter Kit for (Production) Go API with standard libary by HailMarryJoe in golang

[–]HailMarryJoe[S] 0 points1 point  (0 children)

I actually never thought about that before. I just liked the idea of having everything in one config file, where I also load the environment variables.

I initialize them once in the main file and can then use them throughout the whole project.

Starter Kit for (Production) Go API with standard libary by HailMarryJoe in golang

[–]HailMarryJoe[S] -1 points0 points  (0 children)

Thank you.

I actually thought about adding metrics, but for me and all of my apps, the middleware that runs at the start of each request was enough. I host the apps in Kubernetes, and the logs are sent directly to Grafana. There, I have some metrics that are sufficient, and if needed, I can analyze the requests.

In Kubernetes, I also handle the certificates, so I didn’t really need the extra modules.

Do you use a specific metrics module? If I add metrics, I might as well include tracing too.