From b6fc43a5278e2f5bc4d6d8ad73f1e361e1df9717 Mon Sep 17 00:00:00 2001 From: "Ariel Shaqed (Scolnicov)" Date: Wed, 2 Aug 2023 16:05:35 +0300 Subject: [PATCH] Link relative to docs root Test whether that makes %link work --- docs/howto/deploy/aws.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/howto/deploy/aws.md b/docs/howto/deploy/aws.md index 94930ca8c88..1ea9274f112 100644 --- a/docs/howto/deploy/aws.md +++ b/docs/howto/deploy/aws.md @@ -66,7 +66,7 @@ By default, lakeFS will create the required DynamoDB table if it does not alread DEBUG: I am {{ page.path }} ! -💡 You can also use lakeFS with PostgreSQL instead of DynamoDB! See the [configuration reference]({% link /reference/configuration.md%}) for more information. +💡 You can also use lakeFS with PostgreSQL instead of DynamoDB! See the [configuration reference]({% link reference/configuration.md %}) for more information. {: .note } ## Run the lakeFS server @@ -95,7 +95,7 @@ Connect to your EC2 instance using SSH: blockstore: type: s3 ``` -1. [Download the binary]({% link /index.md#downloads%}) to the EC2 instance. +1. [Download the binary]({% link index.md#downloads%}) to the EC2 instance. 1. Run the `lakefs` binary on the EC2 instance: ```sh @@ -133,7 +133,7 @@ To install lakeFS with Helm: ``` 1. Fill in the missing values and save the file as `conf-values.yaml`. For more configuration options, see our Helm chart [README](https://github.com/treeverse/charts/blob/master/charts/lakefs/README.md#custom-configuration){:target="_blank"}. - The `lakefsConfig` parameter is the lakeFS configuration documented [here]({% link /reference/configuration.md%}) but without sensitive information. + The `lakefsConfig` parameter is the lakeFS configuration documented [here]({% link reference/configuration.md%}) but without sensitive information. Sensitive information like `databaseConnectionString` is given through separate parameters, and the chart will inject it into Kubernetes secrets. {: .note }