From ab01e4ad05f65b8e27c5a85ab59bbb0c33b97b95 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Dachary?= Date: Wed, 3 Aug 2022 11:51:38 +0200 Subject: [PATCH] one more example of why gitea dump should not be used --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a6c10c3..ef66ce3 100644 --- a/README.md +++ b/README.md @@ -15,7 +15,7 @@ If Gitea uses a S3 storage for attachments with a PostgresQL database, stores Gi 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: * `gitea dump` to collect everything into one zip file - * `psql/mysql/sqlite dump`. Although the zip file created by `gitea dump` contains a copy of the database it (i) does not work across Gitea versions (it does not have the version table) and (ii) has serious long standing open bugs that may introduce problems when re-injecting the SQL dump in a new database (such as [this one](https://github.com/go-gitea/gitea/issues/8034), or [this one](https://github.com/go-gitea/gitea/issues/19752) or [that one](https://github.com/go-gitea/gitea/issues/12470)). + * `psql/mysql/sqlite dump`. Although the zip file created by `gitea dump` contains a copy of the database it (i) does not work across Gitea versions (it does not have the version table) and (ii) has serious long standing open bugs that may introduce problems when re-injecting the SQL dump in a new database (such as [this one](https://github.com/go-gitea/gitea/issues/8034) or [this one](https://github.com/go-gitea/gitea/issues/19752) or [that one](https://github.com/go-gitea/gitea/issues/12470) or [that one](https://matrix.to/#/!bXIgKPtRdSXHBnVBaz:osgeo.org/$dKg_hMbfmY3lKbnBwsqvlOAwmqfNBm4FR-jcUpBKL5w?via=libera.chat&via=t2bot.io&via=matrix.org)). #### Verify Gitea works