This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Nexus

Planned native Nexus Repository deployment on XCP-ng

This component currently contains a proposal and its OpenSpec validation scaffolding. It contains no service implementation and establishes no deployed state. See the deployment proposal for the agreed scope and design for architecture, dependencies, and remaining deployment inputs.

infra/nexus owns the deployment-specific configuration and documentation. Its planned boundaries are tf_setup for the VM and DNS, ansible for native service deployment, and tf for Nexus API configuration. Reusable service and database behavior belongs to projects/ansible_collection; Vault identities and XO grants remain with infra/vault and infra/xcp_ng. Traefik owns ingress.

The current Bazel targets package documentation and OpenSpec sources only. The owner is registered in the repository’s OpenSpec validation suite. Implementation and live infrastructure operations require later user requests.