From ea2dfd0ea65c2d2ca377543ab1dd12ef0c8f33d8 Mon Sep 17 00:00:00 2001 From: Tana M Berry Date: Fri, 6 Dec 2024 12:38:07 -0600 Subject: [PATCH] add full file extension --- website/docs/developer-docs/setup/full-dev-environment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/developer-docs/setup/full-dev-environment.md b/website/docs/developer-docs/setup/full-dev-environment.md index 9c34e6977e..7462a7b3f7 100644 --- a/website/docs/developer-docs/setup/full-dev-environment.md +++ b/website/docs/developer-docs/setup/full-dev-environment.md @@ -21,7 +21,7 @@ If you use locally installed databases, the PostgreSQL credentials given to auth ::: :::warning -If you are running a [development environment](../../developer-docs/setup/full-dev-environment.md) and you have read replicas configured in your `local.env.yaml` file, you might encounter problems logging back in. This is because dev environments do not have read replica databases, but the `local.env.yaml` file is configured to call them. If you cannot log in, edit your local `.env` file to remove the `postgresql.read_replicas` entry. +If you are running a [development environment](../../developer-docs/setup/full-dev-environment.md) and you have read replicas configured in your `local.env.yaml` file, you might encounter problems logging back in. This is because dev environments do not have read replica databases, but the `local.env.yaml` file is configured to call them. If you cannot log in, edit your local `local.env.yaml` file to remove the `postgresql.read_replicas` entry. ::: ## Backend Setup