hoelee/tubesync
1
0
Fork 0
mirror of https://github.com/meeb/tubesync.git synced 2025-06-18 19:16:36 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Use POSTGRES_DB instead of init.sql

Browse Source
This commit is contained in:
tcely 2025-05-06 18:01:45 -04:00 committed by GitHub
parent dba5bc01a2
commit a2722ee188
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/other-database-backends.md
View File

@ -125,9 +125,9 @@ the DB for the performance benefits, a configuration like this would be enough:
container_name: tubesync-db container_name: tubesync-db
restart: unless-stopped restart: unless-stopped
volumes: volumes:
- /<path/to>/init.sql:/docker-entrypoint-initdb.d/init.sql
- /<path/to>/tubesync-db:/var/lib/postgresql/data - /<path/to>/tubesync-db:/var/lib/postgresql/data
environment: environment:
- POSTGRES_DB=tubesync
- POSTGRES_USER=postgres - POSTGRES_USER=postgres
- POSTGRES_PASSWORD=testpassword - POSTGRES_PASSWORD=testpassword
@ -145,15 +145,3 @@ the DB for the performance benefits, a configuration like this would be enough:
depends_on: depends_on:
- tubesync-db - 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.