docs: update self hosted section (#1230)

Author: bruno-espino

docs/reference/self-hosted/installation.md

@@ -20,15 +20,14 @@ You will require image pull secrets to pull down the docker images from our priv
 
 The Helm chart does not include a production-ready Postgres Database (only a development instance).  You will be required to connect to, and create databases on a Postgres instance.
 
-You will need to create 4 databases, that are used for different things.
+You will need to create 3 databases, that are used for different things.
 
 While we are currently working on running **Logfire** on one database, for now they *must* be separated.
 
-The 4 database in question are:
+The 3 database in question are:
 
 * Standard Postgres Database, i.e, `crud`
 * Object Storage/File Metadata, i.e, `ff`
-* Ingest Database, i.e, `ingest`
 * Dex i.e, `dex`
 
 While they can be named anything, we will refer to them with these identifiers in this guide.
@@ -92,7 +91,7 @@ Here's a checklist you can use to ensure you have all your prerequisites:
 - [ ] Helm CLI Installed
 - [ ] Image Pull Secrets
 - [ ] Access to a Kubernetes cluster
-- [ ] The 4 PostgreSQL database set up
+- [ ] The 3 PostgreSQL databases set up
 - [ ] Identity Provider Configuration
 - [ ] Object Storage Configuration
 - [ ] HTTP Ingress information (i.e, hostname etc.)
@@ -112,7 +111,6 @@ imagePullSecrets:
 
 postgresDsn: postgres://postgres:[email protected]:5432/crud
 postgresFFDsn: postgres://postgres:[email protected]:5432/ff
-postgresIngestDsn: postgres://postgres:[email protected]:5432/ingest
 
 # Configure Dex Postgres & Identity Provider
 
@@ -179,16 +177,15 @@ imagePullSecrets:
 
 ### Postgres Databases
 
-With the 4 databases configured, you will need to configure Logfire & Dex within `values.yaml`.
+With the 3 databases configured, you will need to configure Logfire & Dex within `values.yaml`.
 
-The 3 databases for logfire (`crud`, `ff` and `ingest`) can be configured either via the DSNs in `values.yaml` or as a secret.
+The 2 databases for logfire (`crud` and `ff`) can be configured either via the DSNs in `values.yaml` or as a secret.
 
 I.e,
 
 ```yaml
 postgresDsn: postgres://postgres:[email protected]:5432/crud
 postgresFFDsn: postgres://postgres:[email protected]:5432/ff
-postgresIngestDsn: postgres://postgres:[email protected]:5432/ingest
 ```
 
 Or if you have a secret containing postgresDsn and postgresFFDsn keys: