In this article we are going to cover how we can setup a private go module and then reuse our module in a different application using docker. Firstly let’s quickly go over what exactly a private module is in golang and touch on the spotty history of private modules. Firstly let’s define a private module:
A private module in Golang refers to a self-contained collection of Go code that’s hosted in a private repository, rather than a public one like GitHub. These modules allow developers to encapsulate and share code across multiple projects without making it publicly accessible, ensuring the confidentiality and proprietary nature of the codebase.
Historically, the Go community had a bumpy ride integrating private module support. The initial module system, introduced in Go 1.11, was largely geared towards public repositories. But we now live in the future and it’s the year 1.21 of golang, so let’s get to the nitty gritty of how to use private modules inside go with docker.