From a2722ee18866b198e5ee3d9569d2fc201835dca4 Mon Sep 17 00:00:00 2001
From: tcely <tcely@users.noreply.github.com>
Date: Tue, 6 May 2025 18:01:45 -0400
Subject: [PATCH] Use `POSTGRES_DB` instead of `init.sql`

---
 docs/other-database-backends.md | 14 +-------------
 1 file changed, 1 insertion(+), 13 deletions(-)

diff --git a/docs/other-database-backends.md b/docs/other-database-backends.md
index dbccb579..d623ddd5 100644
--- a/docs/other-database-backends.md
+++ b/docs/other-database-backends.md
@@ -125,9 +125,9 @@ the DB for the performance benefits, a configuration like this would be enough:
   container_name: tubesync-db
   restart: unless-stopped
   volumes:
-   - /<path/to>/init.sql:/docker-entrypoint-initdb.d/init.sql
    - /<path/to>/tubesync-db:/var/lib/postgresql/data
   environment:
+   - POSTGRES_DB=tubesync
    - POSTGRES_USER=postgres
    - POSTGRES_PASSWORD=testpassword
 
@@ -145,15 +145,3 @@ the DB for the performance benefits, a configuration like this would be enough:
   depends_on:
    - tubesync-db
 ```
-
-Note that an `init.sql` file is needed to initialize the `tubesync`
-database before it can be written to. This file should contain:
-
-```
-CREATE DATABASE tubesync;
-```
-
-
-Then it must be mapped to `/docker-entrypoint-initdb.d/init.sql` for it
-to be executed on first startup of the container. See the `tubesync-db`
-volume mapping above for how to do this.