Boilerplating a New Go Program (Microservice)

4 years ago qvault.io

Summary: This is a summary of an article originally published by the source. Read the full original article here →

I lead a team that is responsible for anywhere from 15-25 Go microservices at any given time. I’m mostly writing this article for myself as a kind of self-documentation, but hopefully, you’ll find it useful as you create new Go projects for yourself.

After running cd into our new project, we create an internal directory that will store packages that are meant to be scoped to this project.

Next, we create a cmd folder where we will store all the executable main packages that will be built at compile time.

And the reason for that is Github Actions configurations are VERY dependent on the exact tools you use to deploy your apps.

DevOps Articles