There can be multiple reasons for using a private repository. From a personal perspective, it can be a useful caching mechanism or test-bed when run locally. From an organizational perspective, it's usually about control.
While open source has been fundamental to advancements in every industry that has been touched by the digital era, there's still a case for in-house only code. In some cases, it may be that code is specific to an organization or reveals internal details that should be trade secrets. In other cases, it may be an archaic though impassable proprietary culture. At any rate, it makes all the more sense to share resources when living in a gated community.
In this recipe, we'll investigate setting up a personal module registry that can be deployed as an internal registry to provide a platform for code reuse across an organization...
