From 894b29565858cdbc601987cdaf42de62a97dc107 Mon Sep 17 00:00:00 2001 From: Ishaan Jaff Date: Wed, 13 Nov 2024 16:56:55 -0800 Subject: [PATCH] update doc on pre sync hook --- docs/my-website/docs/proxy/prod.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/my-website/docs/proxy/prod.md b/docs/my-website/docs/proxy/prod.md index 12cfdafc183..14b88e684ad 100644 --- a/docs/my-website/docs/proxy/prod.md +++ b/docs/my-website/docs/proxy/prod.md @@ -1,5 +1,6 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import Image from '@theme/IdealImage'; # ⚡ Best Practices for Production @@ -120,6 +121,14 @@ To ensure only one service manages database migrations, use our [Helm PreSync ho 1. **Helm PreSync Hook**: - The Helm PreSync hook is configured in the chart to run database migrations during deployments. - The hook always sets `DISABLE_SCHEMA_UPDATE=false`, ensuring migrations are executed reliably. + + Reference Settings to set on ArgoCD for `values.yaml` + + ```yaml + db: + useExisting: true # use existing Postgres DB + url: postgresql://ishaanjaffer0324:3rnwpOBau6hT@ep-withered-mud-a5dkdpke.us-east-2.aws.neon.tech/test-argo-cd?sslmode=require # url of existing Postgres DB + ``` 2. **LiteLLM Pods**: - Set `DISABLE_SCHEMA_UPDATE=true` in LiteLLM pod configurations to prevent them from running migrations.