2 KiB
2 KiB
| date | title | slug | weight | toc | draft | menu | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2017-01-01T16:00:00+02:00 | Usage: Backup and Restore | backup-and-restore | 11 | true | false |
|
Backup and Restore
Gitea currently has a dump command that will save the installation to a zip file. This
file can be unpacked and used to restore an instance.
Backup Command (dump)
Switch to the user running gitea: su git. Run ./gitea dump in the gitea installation
directory. There should be some output similar to the following:
2016/12/27 22:32:09 Creating tmp work dir: /tmp/gitea-dump-417443001
2016/12/27 22:32:09 Dumping local repositories.../home/git/gitea-repositories
2016/12/27 22:32:22 Dumping database...
2016/12/27 22:32:22 Packing dump files...
2016/12/27 22:32:34 Removing tmp work dir: /tmp/gitea-dump-417443001
2016/12/27 22:32:34 Finish dumping in file gitea-dump-1482906742.zip
Inside the gitea-dump-1482906742.zip file, will be the following:
custom/conf/app.ini- Server config.gitea-db.sql- SQL dump of databasegitea-repo.zip- Complete copy of the repository directory.log/- Various logs. They are not needed for a recovery or migration.
Intermediate backup files are created in a temporary directory specified either with the
--tempdir command-line parameter or the TMPDIR environment variable.
Restore Command (restore)
There is currently no support for a recovery command. It is a manual process that mostly involves moving files to their correct locations and restoring a database dump.
Example:
apt-get install gitea
unzip gitea-dump-1482906742.zip
cd gitea-dump-1482906742
mv custom/conf/app.ini /etc/gitea/conf/app.ini
unzip gitea-repo.zip
mv gitea-repo/* /var/lib/gitea/repositories/
chown -R gitea:gitea /etc/gitea/conf/app.ini /var/lib/gitea/repositories/
mysql -u$USER -p$PASS $DATABASE <gitea-db.sql
# or sqlite3 $DATABASE_PATH <gitea-db.sql
service gitea restart