From 9fd454a8dddf9fa307526277623b438056991d90 Mon Sep 17 00:00:00 2001 From: Brzozova Date: Mon, 22 Aug 2022 17:21:45 +0200 Subject: [PATCH] Fixing paths to proper destination in main README Old paths lead to 404. Paths have been updated to proper ones. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c5bac4a..3030aee 100644 --- a/README.md +++ b/README.md @@ -2,12 +2,12 @@ We provide Helm charts for two different deployment scenarios: -See the [AWS Single-Instance Resiliency Chart](./https://github.com/sonatype/nxrm3-helm-repository/tree/main/aws-single-instance-resiliency) if you are doing the following: +See the [AWS Single-Instance Resiliency Chart](https://github.com/sonatype/nxrm3-helm-repository/tree/main/aws-single-instance-resiliency) if you are doing the following: * Deploying Nexus Repository Pro to an AWS cloud environment with the desire for automatic failover across Availability Zones (AZs) within a single region * Planning to configure a single Nexus Repository Pro instance within your Kubernetes/EKS cluster with two or more nodes spread across different AZs within an AWS region * Using an external PostgreSQL database (required) -See the [Single-Instance OSS/Pro Kubernetes Chart](./https://github.com/sonatype/nxrm3-helm-repository/tree/main/single-inst-oss-pro-kubernetes) if you are doing the following: +See the [Single-Instance OSS/Pro Kubernetes Chart](https://github.com/sonatype/nxrm3-helm-repository/tree/main/single-inst-oss-pro-kubernetes) if you are doing the following: * Using embedded OrientDB (required) * Deploying either Nexus Repository Pro or OSS to an on-premises environment with bare metal/VM server (Node) * Deploying a single Nexus Repository instance within a Kubernetes cluster that has a single Node configured