Skip to content

j-s-3/nexus-vagrant

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

44 Commits
 
 
 
 
 
 
 
 

Repository files navigation

This is a Vagrant Environment for a Nexus Repository OSS service.

This will:

  • Configure Nexus through Groovy scripts.
    • Create the adhoc-package repository.
    • Create the npm-group, npm-hosted and npmjs.org-proxy repositories.
    • Create the chocolatey-group, chocolatey-hosted and chocolatey.org-proxy repositories.
    • Create the powershell-group, powershell-hosted and powershellgallery.com-proxy repositories.
    • Configure the NuGet nuget-hosted repository to accept pushing with an API key.
    • Schedule a task to remove the old snapshots from the maven-snapshots repository.
    • Create users and a custom deployer role.
    • Setup an Active Directory LDAP user authentication source (when config_authentication='ldap' is set inside the provision-nexus.sh file).
    • For more details look inside the provision/provision-nexus directory.
  • Setup nginx as a Nexus HTTPS proxy and static file server.
  • Test the installed repositories by using and publishing to them (see the use-* files).

NB If you are new to Groovy, be sure to check the Groovy Learn X in Y minutes page.

Caveats

  • Most of the repository plugins are not open-source.
    • Only maven and raw are open-source.

Usage

Build and install the Ubuntu Base Box.

Build and install the Windows Base Box.

Add the following entry to your /etc/hosts file:

192.168.56.3 nexus.example.com

Install Vagrant 2.1+.

Run vagrant up --provider=virtualbox # or --provider=libvirt to launch the environment. See its output to known how to login at the local Nexus home page as admin (you can also login with one of the example accounts, e.g. alice.doe and password password).

NB nginx is setup with a self-signed certificate that you have to trust before being able to access the local Nexus home page.

Notes

Check for a component existence

With bash, HTTPie and jq:

function nexus-component-exists {
  [ \
    "$(
      http \
        get \
        https://nexus.example.com/service/rest/beta/search \
        "repository==$1" \
        "name==$2" \
        "version==$3" \
      | jq -r .items[].name)" == "$2" \
  ]
}

if nexus-component-exists npm-hosted hello-world 1.0.0; then
  echo 'component exists'
else
  echo 'component does not exists'
fi

With PowerShell:

function Test-NexusComponent {
  param(
    [string]$repository,
    [string]$name,
    [string]$version)
  $items = (Invoke-RestMethod `
    -Method Get `
    -Uri https://nexus.example.com/service/rest/beta/search `
    -Body @{
      repository = $repository
      name = $name
      version = $version
    }).items
  $items.Count -and ($items.name -eq $name)
}

if (Test-NexusComponent npm-hosted hello-world 1.0.0) {
  Write-Host 'component exists'
} else {
  Write-Host 'component does not exists'
}

Troubleshooting

Logs

The logs are at /opt/nexus/log/nexus.log.

You can also see them with journalctl -u nexus.

OrientDB

Nexus uses OrientDB as its database. To directly use it from the console run:

systemctl stop nexus
su nexus -s /bin/bash -c 'cd /opt/nexus && java -jar ./lib/support/nexus-orient-console.jar'

Then connect to one of the databases, e.g. to the security database:

connect plocal:nexus3/db/security admin admin

Then execute some commands, e.g.:

help
list classes

For more information about the console see Running the OrientDB Console.

Reference

About

Vagrant Environment for a Nexus Repository OSS service

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Shell 44.2%
  • PowerShell 26.8%
  • Groovy 25.6%
  • Makefile 1.5%
  • JavaScript 1.1%
  • HTML 0.8%