.

Author: gregsadetsky

docs/exhaustive-documentation/crons.md

@@ -1,7 +1,3 @@
----
-sidebar_position: 2
----
-
 # Crons
 
 You can specify crons in your `disco.json` file:

docs/exhaustive-documentation/environment-variables.md

@@ -1,7 +1,3 @@
----
-sidebar_position: 1
----
-
 # Environment Variables
 
 To set environment variables for you project, you can use the CLI commands:

docs/exhaustive-documentation/images.md

@@ -1,7 +1,3 @@
----
-sidebar_position: 6
----
-
 # Images
 
 Each service uses a Docker image.

docs/exhaustive-documentation/ports.md

@@ -1,8 +1,4 @@
----
-sidebar_position: 7
----
-
-# Ports
+# Network Ports
 
 ## Web
 

docs/exhaustive-documentation/postgresql-simplified.md

@@ -0,0 +1,28 @@
+# PostgreSQL
+
+disco provides a "good enough" Postgres addon.
+
+## Introduction
+
+disco provides a "good enough" Postgres addon.
+
+This addon is a great way to quickly setup a database when Postgres is not mission critical to your system. If you need any non-basic features, like replication, automatic failover, monitoring, automatic backups and restore, etc. you should consider using a managed Postgres provider, such as [Neon](https://neon.tech/) or [Supabase](https://supabase.com/).
+
+## How to add Postgres to your project
+
+We assume that you've deployed a project using disco.
+
+Once your project is live, you can run the following command:
+
+```bash
+disco postgres:create --project PROJECTNAME
+```
+
+replacing `PROJECTNAME` with the name of your project.
+
+This command will provision a Postgres database and attach it to your project. Once it's done, an environment variable named `DATABASE_URL` will be added to your project. This variable will contain the URL to your Postgres database.
+
+---
+
+You can read more about the Postgres addon in the [advanced docs](/docs/exhaustive-documentation/postgresql.md).
+

docs/exhaustive-documentation/postgresql.md

@@ -1,14 +1,10 @@
----
-sidebar_position: 4
----
+# PostgreSQL (Advanced)
 
-# PostgreSQL
+## Introduction
 
-Disco provides a "good enough" Postgres addon.
+disco provides a "good enough" Postgres addon.
 
-## Good Enough
-
-The Postgres addon is a great way to quickly have access to Postgres when Postgres is not mission critical to your system. If you need any non-basic features, like replication, automatic failover, monitoring, automatic backups and restore, etc. you should use a more serious solution, like a managed Postgres.
+This addon is a great way to quickly setup a database when Postgres is not mission critical to your system. If you need any non-basic features, like replication, automatic failover, monitoring, automatic backups and restore, etc. you should consider using a managed Postgres provider, such as [Neon](https://neon.tech/) or [Supabase](https://supabase.com/).
 
 ## TL;DR
 

docs/exhaustive-documentation/volumes.md

@@ -1,7 +1,3 @@
----
-sidebar_position: 5
----
-
 # Volumes
 
 In some cases, you may need to store data that outlives a container lifetime. You can achieve this using volumes.

docs/exhaustive-documentation/worker-processes.md

@@ -1,7 +1,3 @@
----
-sidebar_position: 3
----
-
 # Worker Processes
 
 In your `disco.json` file, you can define many services. The one that has the name `web` will be exposed to the internet by Disco. The other ones will just run.