Member-only story
Having a Docker Container As Your Private NPM Registry — The Easy Way
Change your Azure Docker Container Instance to a private NPM registry with Azure Container Registry
Introduction
At some point in our lives, we need almost everything in a private scope, and that includes your NPM packages. You may have created a private NPM package for your company or yourself and wanted to host it somewhere. You might have seen options like a paid version of npm, but in this piece, we are going to change our Docker container instance to a private NPM registry, and once it is ready, you can host your private npm packages on that registry. Let’s jump into it.
Background
As I mentioned before, I am going to create a container instance and change it to a private NPM registry. I will be using Microsoft Azure.
Setting up a Docker Private NPM Registry
To create the Azure Container Registry, you should have a valid Azure subscription. If you don’t have one, please get one; it will help you follow this piece. Once you get an Azure subscription, you are ready to start.
