There are often times in agile teams where DevOps is constrained by bandwidth.
This tutorial is aimed at developers to help them get things up and running without hassle. This will give them confidence to try out things on a working instance rather than just learning theory.
In this video I divided entire tutorial into series of steps. There are just four, called out from step one to step 4.1.
Step 1 is needed to download the exe from Nexus host.
Step 2 is needed because the downloaded package is in .zip format for Windows and .tgz for Linux.
Step 3 is responsible for running the Nexus server. Behind-the-scenes it does many things so that a normal developer need not have to worry. If you are running this on Linux you can start this process in background with "&" added at the end of the command.
Step 3.1 may be needed if you have existing application running on the same port as Linux. This will only be evident when you fail.
Step 4 is the general step that allows you to login to the Nexus server. Since you will be logging in for the first time, you need to refer to admin.password file to get the temp password.
Step 4.1 allows you to change the password from the default password. This will also remove the admin.password file. Do remember the password that you create!
One of the key motivation for using Nexus Repository is its ease of use. It is easy configure. It greatly helps getting a team up and running with repository manager. There are two versions. The Pro version has extended capabilities and support. There is also an open source version (Nexus Repository OSS) as well so teams can get started with it right away.