-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discuss manual backup (gitea dump) #448
Comments
You are right! And I think we need an enhanced dump which could dump-mysql or dump-sqlite and a restore command. Please feel free to send PR to go-gitea/docs to help us improve the documents. |
Maybe we can really integrate a restore command that imports everything that have been dumped before. |
Of course we will. |
I have a branch for that |
Please send a PR. |
So I think this issue has been resolved for your PR? And now we need a restore command, but that should be another issue or PR. |
Hello everyone,
Reposting gogs/gogs#2924 so that we can keep track of it here.
There is a hidden command called
dump
that creates a zip file with the config (custom/conf/app.ini
),gitea-db.sql
and a nested zip of the repos.It would be really good to have this behavior documented on the website, and also some tips on how to perform a restore. The way I see it, one can download a fresh binary of gitea, set up the same file structure and somehow import the sql file. I personally have very little experience with SQL so am not sure how this is done.
I'm in the middle of moving servers, so would be happy to be the guinea pig on migrating a gitea installation. I'm also a huge fan of markdown so can help with documentation if needed.
The text was updated successfully, but these errors were encountered: