add note about adding sslmode=disable to the db connection string (#287)

stellar · Dec 19, 2023 · 010fb1d · 010fb1d
1 parent 5aafab0
commit 010fb1d
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/run-api-server/configuring.mdx b/docs/run-api-server/configuring.mdx
@@ -35,7 +35,7 @@ You'll see that Horizon defines a large number of flags; however, only a handful
 | `--db-url` | `DATABASE_URL` | postgres://localhost/horizon_testnet |
 | `--history-archive-urls` | `HISTORY_ARCHIVE_URLS` | https://history.stellar.org/prd/core-testnet/core_testnet_001,https://history.stellar.org/prd/core-testnet/core_testnet_002 |
 
-- The most important parameter, `--db-url`, specifies the Horizon database; its value should be a valid [PostgreSQL Connection URI](http://www.postgresql.org/docs/9.6/static/libpq-connect.html#AEN46025).
+- The most important parameter, `--db-url`, specifies the Horizon database; its value should be a valid [PostgreSQL Connection URI](http://www.postgresql.org/docs/9.6/static/libpq-connect.html#AEN46025). If you are running horizon locally, you may want to add the `sslmode=disable` query parameter to the connection string, although this is not recommended in production environments.
 - The other parameter, `--history-archive-urls`, specifies a set of comma-separated locations from which Horizon should download [history archives](../run-core-node/publishing-history-archives.mdx).
 
 #### With Ingestion