From 20aae707d1c31974aa18c75b6300d6f08e75601a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Dachary?= Date: Tue, 9 May 2023 17:20:20 +0200 Subject: [PATCH] docs: forgejo dump has the SQLite db, no need to dump --- admin/upgrade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/admin/upgrade.md b/admin/upgrade.md index 6397f7dd..98dd4d50 100644 --- a/admin/upgrade.md +++ b/admin/upgrade.md @@ -20,7 +20,7 @@ However, if Forgejo uses a S3 storage for attachments with a PostgresQL database In the simplest case where everything is on a single file system and if the instance is not busy (no mirrors, no users), the backup can be done with: - `forgejo dump` to collect everything into one zip file -- `psql/mysql/sqlite dump`. Although the zip file created by `forgejo dump` contains a copy of the database it has serious long standing open bugs that may introduce problems when re-injecting the SQL dump in a new database. +- `psql/mysql/mssql dump`. Although the zip file created by `forgejo dump` contains a copy of the database it has serious long standing open bugs that may introduce problems when re-injecting the SQL dump in a new database. Note that there is no need to dump SQLite because the database itself is included in the zip file already. ### Verify Forgejo works