Update database from Git Repositories #4220

New Issue

GiteaMirror · 2025-11-02T05:42:50-06:00

GiteaMirror commented

2025-11-02 05:42:50 -06:00

Originally created by @tcyrus on GitHub (Nov 1, 2019).

Gitea version (or commit ref): 1.9.2
Git version: N/A
Operating system: Ubuntu
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- 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".

Originally created by @tcyrus on GitHub (Nov 1, 2019).   - 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".

GiteaMirror added the type/question issue/confirmed labels 2025-11-02 05:42:50 -06:00

GiteaMirror closed this issue

2025-11-02 05:42:51 -06:00

GiteaMirror commented

2025-11-02 05:42:51 -06:00

@guillep2k commented on GitHub (Nov 1, 2019):

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 commented on GitHub (Nov 1, 2019): 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.

GiteaMirror commented

2025-11-02 05:42:51 -06:00

@guillep2k commented on GitHub (Nov 1, 2019):

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

@guillep2k commented on GitHub (Nov 1, 2019): This, however, could be an interesting function for a Gitea utility to have.

GiteaMirror commented

2025-11-02 05:42:52 -06:00

@zeripath commented on GitHub (Nov 1, 2019):

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?

@zeripath commented on GitHub (Nov 1, 2019): 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?

GiteaMirror commented

2025-11-02 05:42:52 -06:00

@guillep2k commented on GitHub (Nov 1, 2019):

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

@guillep2k commented on GitHub (Nov 1, 2019): > > > 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. 😁

GiteaMirror commented

2025-11-02 05:42:52 -06:00

@stale[bot] commented on GitHub (Jan 1, 2020):

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.

@stale[bot] commented on GitHub (Jan 1, 2020): 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.

GiteaMirror commented

2025-11-02 05:42:52 -06:00

@lunny commented on GitHub (Jan 1, 2020):

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

@lunny commented on GitHub (Jan 1, 2020): Since `push to create feature` has been implemented, I think we can close this now.

GiteaMirror commented

2025-11-02 05:42:52 -06:00

@stale[bot] commented on GitHub (Mar 1, 2020):

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.

@stale[bot] commented on GitHub (Mar 1, 2020): 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.

GiteaMirror referenced this issue

2025-11-02 12:31:47 -06:00

[PR #4220] [MERGED] Fix swagger errors #17289

GiteaMirror referenced this issue

2025-11-02 12:31:58 -06:00

[PR #4236] [MERGED] Fix swagger security part #17297

GiteaMirror referenced this issue

2025-11-02 12:32:02 -06:00

[PR #4239] [MERGED] fix CreateIssueCommentOption reference #17300

Sign in to join this conversation.