please work

website/docs/developer-docs/setup/full-dev-environment.md

@@ -20,6 +20,10 @@ You can also use a native install, if you prefer.
 If you use locally installed databases, the PostgreSQL credentials given to authentik should have permissions for `CREATE DATABASE` and `DROP DATABASE`, because authentik creates a temporary database for tests.
 :::
 
+:::warning
+If you are running a development environment 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
 
 :::info

website/docs/install-config/configuration/configuration.mdx

@@ -99,6 +99,10 @@ The same PostgreSQL settings as described above are used for each read replica.
 
 Note that `USE_PGBOUNCER` and `USE_PGPOOL` are inherited from the main database configuration and are _not_ overridable on read replicas.
 
+:::warning
+If you are running a [development environment](../../developer-docs/setup/full-dev-environment.md) be aware that read replicas are not supported.
+:::
+
 ## Redis Settings
 
 - `AUTHENTIK_REDIS__HOST`: Redis server host when not using configuration URL