-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Update database from Git Repositories #8774
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
Comments
You can enable |
This, however, could be an interesting function for a Gitea utility to have. |
Yeah I think we should make it possible recover data - however, it's a slightly difficult situation. With a completely brand new Gitea do you create users for each of the recovered repositories? - but they might have meant to be organisations so this is probably not correct. So you should probably leave it till users are created - and then restore? |
It's pretty easy: recreate those that have a matching user, report those that don't. 😁 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
Since |
This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions. |
[x]
):Description
My database server had an issue unrelated to Gitea, but I lost some of the database records. I restored a backup of the database, but some of the repositories are missing from this copy.
I was wondering if there was an admin command to do the reverse of "Reinitialize all missing Git repositories for which records exist", where it would "Reinitialize all missing records for which Git repositories exist".
The text was updated successfully, but these errors were encountered: