Gitea: Update database from Git Repositories

[tcyrus]

• Gitea version (or commit ref): 1.9.2
• Git version: N/A
• Operating system: Ubuntu
• Database (use [x]):
  
  
  
  • [X] PostgreSQL
  
  
  • [ ] MySQL
  
  
  • [ ] MSSQL
  
  
  • [ ] SQLite
  
  
• Can you reproduce the bug at https://try.gitea.io:
  
  
  
  • [ ] Yes (provide example URL)
  
  
  • [ ] No
  
  
  • [X] Not relevant
  
  
• Log gist:

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".

[guillep2k]

You can enable IMPORT_LOCAL_PATHS = true in app.ini and manually import those repositories. They will be created anew in the database; no issues/PRs/labels/etc will exist but the code will be there. For this to work you must first move them out of their current location (i.e. from gitea-repositories/{owner}/... to another directory).
I know it isn't much, but may be it will help.

[guillep2k]

This, however, could be an interesting function for a Gitea utility to have.

[zeripath]

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?

[guillep2k]

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. 😁

[stale[bot]]

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.

[lunny]

Since push to create feature has been implemented, I think we can close this now.

[stale[bot]]

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.