How to backup, restore and migrate #6876
Replies: 6 comments 5 replies
-
|
When running gogs inside a Docker container (named 'gogs' in my case) I use: This first removes old back-ups inside the container, then makes a new back-up inside the docker container, copies the file to the current location (outside the container) and removes the backup from within the container again. It also makes an MD5 hash of the made back-up. Inspired by: #4339 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for sharing! |
Beta Was this translation helpful? Give feedback.
-
|
thanks ! |
Beta Was this translation helpful? Give feedback.
-
|
Damn it, it took me 5 hours to finally find a solution. Thank you for sharing. |
Beta Was this translation helpful? Give feedback.
-
|
I ran restore command with success. I checked the db and see it has restored the users and it has restored the repositories. However, I cannot login to my account. It returns error that username or password is incorrect. I checked the user table and see the users, but the password field is blank. Perhaps that's the issue. Shouldn't the restore operation restore user passwords also. Hoping there is a fix for this. Kindly advise. Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
same here |
Beta Was this translation helpful? Give feedback.
-
|
请问你解决这个问题了嘛？ |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, nobody on gogs offers to help so I ditched it. I moved over to gitea on docker and it's superior. |
Beta Was this translation helpful? Give feedback.
-
|
what i did for gogs helm chart: kubectl exec -n gogs <pod name> -- bash -c "HOME=/data/git USER=git /app/gogs/gogs backup --target /backup"
kubectl cp -n gogs <pod name>:/backup/<file> ./<file>in destination gogs (make sure its running 1/1): kubectl cp -n gogs ./<file> <pod name>:/backup/<file>
kubectl exec -n gogs <pod name> -- bash -c "mkdir /data/tmp; HOME=/data/git USER=git /app/gogs/gogs restore --from /backup/<file> -t /data/tmp; chown -R git:git /data" |
Beta Was this translation helpful? Give feedback.
-
|
I get an error when I want to migrate sqlite3 to postgresql |
Beta Was this translation helpful? Give feedback.
-
|
This ignores --config in both backup and restore, no matte what I try |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Other than pack up
gogs-repositories,data,customand database separately, Gogs provides two commands for unified process of backup, restore and even migrate to another database engine, because the backup format is database-agnostic.Prerequisite
Backup
Go to the directory where your Gogs binary is located, and execute following command:
Without any flags,
backupcommand will pack up allgogs-repositories,data,customand database into a single zip archive (e.g.gogs-backup-xxx.zip) under the current directory.It could be a bad idea if your
gogs-repositoriescontains GB of raw data, in that case, you can apply--exclude-reposflag:If your
custom/conf/app.iniis somewhere unusual, make sure you specify it via--configflag like always:Database
If you're only interested in backup your database, or want to migrate from one database engine (e.g. SQLite3) to another engine (e.g. PostgreSQL),
--database-onlyis your friend:The backup format of database are portable JSON files, each file corresponds to a database table, you can do whatever you want with those files.
Restore
The
restorecommand also has flags to indicate only restore database or everything in backup archive:If a table that is not presented in backup archive, whatever in current database table will remain unchanged.
Custom config file
There are 2 steps to determine which
custom/conf/app.inicommand uses:If both steps failed, sorry, impossible to perform restore process.
Beta Was this translation helpful? Give feedback.
All reactions