Hostea
/
admin-guide
3
1
Fork 1
Code Issues Pull Requests Releases Activity

one more example of why gitea dump should not be used

master
Loïc Dachary 2022-08-03 11:51:38 +02:00
parent 09bdc0d476
commit ab01e4ad05
Signed by: dachary
GPG Key ID: 992D23B392F9E4F2
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -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