From 0757c99f0173f5c01f9f8ca338bbe64ed11fde4e Mon Sep 17 00:00:00 2001 From: meeb Date: Sun, 9 Jan 2022 12:24:55 +1100 Subject: [PATCH] doc tweaks, feedback from #195 --- docs/other-database-backends.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/other-database-backends.md b/docs/other-database-backends.md index 2b339b9f..3aa4660a 100644 --- a/docs/other-database-backends.md +++ b/docs/other-database-backends.md @@ -13,18 +13,18 @@ become an issue. TubeSync supports SQLite (the automatic default) as well as PostgreSQL, MySQL and MariaDB. For MariaDB just follow the MySQL instructions as the driver is the same. -You should a blank install of TubeSync. Migrating to a new database will reset your -database. If you are comfortable with Django you can export and re-import existing -database data with: +You should start with a blank install of TubeSync. Migrating to a new database will +reset your database. If you are comfortable with Django you can export and re-import +existing database data with: ```bash -$ docker exec -ti tubesync python3 /app/manage.py dumpdata > some-file.json +$ docker exec -i tubesync python3 /app/manage.py dumpdata > some-file.json ``` Then change you database backend over, then use ```bash -$ cat some-file.json | docker exec -ti tubesync python3 /app/manage.py loaddata --format=json - +$ cat some-file.json | docker exec -i tubesync python3 /app/manage.py loaddata --format=json - ``` As detailed in the Django documentation: