Directories
The binary archive for Nexus Repository contains the following two directories.
Installation Directory
$install-dir
- This directory contains the Nexus Repository application, the Java libraries, and configuration files. Throughout the documentation, this is referred to as the install-dir.
This directory is replaced when upgrading Nexus Repository. New versions of Nexus Repository commonly include modifications to the basic configuration as features are added and removed. Configuration stored in these files must be copied to the new installation directory during the upgrade.
Modifying Configuration
We recommend storing configuration changes to the override files found in the data directory.
OSS-LICENSE.txt | NOTICE.txt
These are files that contain legal details about the license and copyright notices
bin/
This directory contains the startup script itself as well as startup-related configuration files.
deploy/
This directory contains a placeholder.
etc/
This directory contains configuration files.
system/
This directory contains all components and plugins that constitute the application.
jdk/
The embedded JVM used by Nexus Repository.
Data Directory
$data-dir
- This directory contains everything stored and managed by Nexus Repository. This directory persists between upgrades with files being created during the operation of Nexus Repository.
The default location of the data directory is sonatype-work/nexus3
relative to the installation directory.
Files and directories under the data directory include:
blobs/
The default directory for file system-based blob stores when defined with a relative path. The default blob store is at the following path.
sonatype-work/nexus3/blobs/default
Tip
We recommend configuring blob stores outside of the sonatype work direction for resilient and highly available (HA) deployments. This is required for shared artifact storage and eases backup and recovery.
See Storage Guide
cache/
This directory contains information on currently cached Karaf bundles
db/
This directory contains the H2 database which is the primary storage for your metadata. This directory is not used when using an external PostgreSQL.
elasticsearch/
This directory contains the currently configured state of Elasticsearch
etc/
This directory contains the main runtime configuration and customization.
health-check/
This directory contains cached reports from the Repository Health Check feature
keystores/
This contains the automatically generated key used to identify your repository manager
log/
This directory and sub-directories contain active and archived application log files.
See Logging for details on the log files.
tmp/
This directory is used for temporary storage.