github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-14 11:56:41 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Import repositories from broken gitea #2985

New Issue
Closed
opened 2025-11-02 04:56:12 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 04:56:12 -06:00
Owner
Copy Link

Originally created by @LunaTheFoxgirl on GitHub (Feb 27, 2019).

  • Gitea version (or commit ref): cbfc7f5
  • Git version: 2.11.0
  • Operating system: Debian Linux
  • 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:
    Wiped logs as they were 22 GB in size

Description

Earlier today my gitea server went offline, when i checked at home the server had run out of space, looking in to it; XORM had created a 22 GB log file breaking the database and making the system very unresponsive.

I deleted all the logs and tried to use the database but as stated, it was corrupted.

How can i import the repositories from the old gitea version to the "fresh" version?
Since i've had to remove the database.

I have the gitea-repositories folder.
...

Screenshots

Originally created by @LunaTheFoxgirl on GitHub (Feb 27, 2019). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): cbfc7f5 - Git version: 2.11.0 - Operating system: Debian Linux - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: Wiped logs as they were 22 GB in size ## Description Earlier today my gitea server went offline, when i checked at home the server had run out of space, looking in to it; XORM had created a 22 GB log file breaking the database and making the system very unresponsive. I deleted all the logs and tried to use the database but as stated, it was corrupted. How can i import the repositories from the old gitea version to the "fresh" version? Since i've had to remove the database. I have the gitea-repositories folder. ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/question label 2025-11-02 04:56:12 -06:00
GiteaMirror commented 2025-11-02 04:56:13 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 28, 2019):

Copy gitea-repositories, data, custom and dump your databases and paste to your new machine.

@lunny commented on GitHub (Feb 28, 2019): Copy `gitea-repositories`, `data`, `custom` and dump your databases and paste to your new machine.
GiteaMirror commented 2025-11-02 04:56:13 -06:00
Author
Owner
Copy Link

@LunaTheFoxgirl commented on GitHub (Feb 28, 2019):

Can’t dump database, it is corrupted.

Is there any way to import the raw git repos from gitea-repositories? I don't mind that i'll have to recreate issues and such.

@LunaTheFoxgirl commented on GitHub (Feb 28, 2019): Can’t dump database, it is corrupted. Is there any way to import the raw git repos from gitea-repositories? I don't mind that i'll have to recreate issues and such.
GiteaMirror commented 2025-11-02 04:56:13 -06:00
Author
Owner
Copy Link

@saitho commented on GitHub (Mar 19, 2019):

Git repositories are stored on the file system, not in the database. Still the database is used for displaying information on the web interface.

I had a similar issue a few weeks ago. I moved Gitea to another server and forgot to adjust the database configuration. The old server was shut down and my database was lost.

I still had all my repositories on the file system and restored the database by creating a new repository via the web interface and restored the old repository files. It took me some time to figure out that Gitea uses Git hooks to retrieve the changes from commits and show the files on the web interface.

At least that worked for me, running Gitea in a Docker container...

I went into the folder with the repositories and did this for each repository I wanted to restore:

  1. Backup repository folder: mv my-repository.git my-repository.git-bak
  2. Create a new repository with the same name via the Gitea GUI
  3. Remove the folder that is created: rm -rf my-repository.git
  4. Restore the saved repository: cp -R my-repository.git-bak my-repository.git
  5. Set correct permissions: chown -R git:git my-repository.git
  6. Set execution permissions for Git hooks: chmod -R +x my-repository.git/hooks/*
  7. As of right now you should still see no files on the repository page on Gitea
  8. Clone the repository: git clone git@my-gitea.com:user/my-repository.git
  9. Make a change to the local repository and push it: touch test.txt && git add . && git commit -m "Test" && git push -u origin master
  10. Check the repository page on Gitea. The files should show up.
  11. Revert the last commit by changing “pick” on the second line to “d”: git rebase -i HEAD~2 && git push -f
@saitho commented on GitHub (Mar 19, 2019): Git repositories are stored on the file system, not in the database. Still the database is used for displaying information on the web interface. I had a similar issue a few weeks ago. I moved Gitea to another server and forgot to adjust the database configuration. The old server was shut down and my database was lost. I still had all my repositories on the file system and restored the database by creating a new repository via the web interface and restored the old repository files. It took me some time to figure out that Gitea uses Git hooks to retrieve the changes from commits and show the files on the web interface. At least that worked for me, running Gitea in a Docker container... I went into the folder with the repositories and did this for each repository I wanted to restore: 1. Backup repository folder: `mv my-repository.git my-repository.git-bak` 2. Create a new repository with the same name via the Gitea GUI 3. Remove the folder that is created: `rm -rf my-repository.git` 4. Restore the saved repository: `cp -R my-repository.git-bak my-repository.git` 5. Set correct permissions: `chown -R git:git my-repository.git` 6. Set execution permissions for Git hooks: `chmod -R +x my-repository.git/hooks/*` 7. As of right now you should still see no files on the repository page on Gitea 8. Clone the repository: `git clone git@my-gitea.com:user/my-repository.git` 9. Make a change to the local repository and push it: `touch test.txt && git add . && git commit -m "Test" && git push -u origin master` 10. Check the repository page on Gitea. The files should show up. 11. Revert the last commit by changing “pick” on the second line to “d”: `git rebase -i HEAD~2 && git push -f`
GiteaMirror commented 2025-11-02 04:56:13 -06:00
Author
Owner
Copy Link

@LunaTheFoxgirl commented on GitHub (Mar 19, 2019):

I've decided to switch back to github for now, though thanks for the suggestion.

@LunaTheFoxgirl commented on GitHub (Mar 19, 2019): I've decided to switch back to github for now, though thanks for the suggestion.
GiteaMirror commented 2025-11-02 04:56:13 -06:00
Author
Owner
Copy Link

@TheRojam commented on GitHub (Sep 20, 2020):

I've decided to switch back to github for now, though thanks for the suggestion.

nice.. but that not a solution, that only a workaround... sad

@TheRojam commented on GitHub (Sep 20, 2020): > I've decided to switch back to github for now, though thanks for the suggestion. nice.. but that not a solution, that only a workaround... sad
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2985
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?