docs: self-hosted improvements (#1222)

Author: bruno-espino

docs/reference/self-hosted.md

@@ -42,7 +42,8 @@ Our [full installation guide](../self-hosted/installation.md) provides a complet
 #### Development-Only Options
 For quick testing or development, the chart can deploy internal instances of Postgres and MinIO. These are enabled with the ```dev.deployPostgres``` and ```dev.deployMinio flags```.
 
-:warning: **Warning:** These development services are not suitable for production use. They lack persistence, backup, and security configurations.
+!!! warning
+    These development services are not suitable for production use. They lack persistence, backup, and security configurations.
 
 ### Installation
 

docs/self-hosted/installation.md

@@ -2,7 +2,7 @@
 
 Installation of the self-hosted **Logfire** requires that you have a few prerequisites before installing.
 
-## Gathering Prerequisites
+## Prerequisites
 
 ### Helm CLI
 
@@ -14,20 +14,21 @@ When running the helm chart, you will be required to create resources within a K
 
 ### Image Pull Secrets
 
-You will require image pull secrets to pull down the docker images from our private repository.  Get in contact with us to get a copy of them.
+You will require image pull secrets to pull down the docker images from our private repository. Contact us at [[email protected]](mailto:[email protected]) to get a copy.
 
 ### Postgres Database
 
 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 3 databases, that are used for different things.
+You will need to create 4 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 3 database in question are:
+The 4 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.
@@ -91,7 +92,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 3 PostgreSQL database set up
+- [ ] The 4 PostgreSQL database set up
 - [ ] Identity Provider Configuration
 - [ ] Object Storage Configuration
 - [ ] HTTP Ingress information (i.e, hostname etc.)
@@ -107,10 +108,11 @@ adminEmail: [email protected]
 imagePullSecrets:
   - logfire-image-key
 
-# Configure Postgres Databases
+# Configure Logfire Postgres Databases
 
 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
 
@@ -156,7 +158,7 @@ This uses Amazon S3 as an Object Store, and Github as an Identity Provider, but
 
 ### Image Pull Secrets
 
-You will require image pull secrets to pull down the docker images from our private repository.  Get in contact with us to get a copy of them.
+You will require image pull secrets to pull down the docker images from our private repository. Contact us at [[email protected]](mailto:[email protected]) to get a copy.
 
 When you have the `key.json` file you can load it in as a secret like so:
 
@@ -179,16 +181,21 @@ imagePullSecrets:
 
 With the 4 databases configured, you will need to configure Logfire & Dex within `values.yaml`.
 
-The 2 databases for logfire (`crud` and `ff`) can be configured either via the DSNs in `values.yaml` or as a secret.
+The 3 databases for logfire (`crud`, `ff` and `ingest`) 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:
+Or if you have a secret containing postgresDsn and postgresFFDsn keys:
+
+!!! note
+    For ArgoCD users, it is highly recommended to [use an existing Kubernetes secret](https://argo-cd.readthedocs.io/en/stable/operator-manual/secret-management/) to manage your database credentials.
+    To do so, ensure you set `enabled: true` and provide the name of your secret.
 
 ```yaml
 postgresSecret:

docs/self-hosted/troubleshooting.md

@@ -2,6 +2,14 @@
 
 There are occasions when you need to troubleshoot the installation.  Since Logfire sends its own internal logs to the `logfire-meta` organisation, this is a good place to start.
 
+## ErrImagePull / ImagePullBackOff
+
+If you are seeing Image pull issues on your logfire pods, make sure you have:
+
+* Created the required Image Pull Secret as described at the [Installation](./installation.md#image-pull-secrets_1) section
+* You set the right secret name at `Values.imagePullSecrets`
+* Both secret and the release are installed on the same namespace
+
 ## Accessing the Meta Organization
 
 Logfire will send internal traces to a meta organisation that is created upon first install.   This meta organisation is helpful in troubleshooting any issues that might arise when running Logfire.