Git to Gitea migration #5704

New Issue

GiteaMirror · 2025-11-02T06:33:34-06:00

GiteaMirror commented

2025-11-02 06:33:34 -06:00

Originally created by @kinos9 on GitHub (Jul 7, 2020).

Gitea version (or commit ref): 1.12.1
Git version: 2.7.4
Operating system: Ubuntu 16.04 Server
Database:
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant

Description

I actually have a git server (git version 2.7.4) with some repositories. They are maintained under git user.
Now I have installed gitea (with dedicated gitea user) I would like to access to existent repositories for example linking the directory where they are stored now: /home/gitea/gitea-repositories/kinos -> /srv/git (this is the first thing that I thought).
Is this possible?

Thx,
K

Originally created by @kinos9 on GitHub (Jul 7, 2020). - Gitea version (or commit ref): 1.12.1 - Git version: 2.7.4 - Operating system: Ubuntu 16.04 Server - Database: - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant ## Description I actually have a git server (git version 2.7.4) with some repositories. They are maintained under `git` user. Now I have installed gitea (with dedicated `gitea` user) I would like to access to existent repositories for example linking the directory where they are stored now: `/home/gitea/gitea-repositories/kinos -> /srv/git` (this is the first thing that I thought). Is this possible? Thx, K

GiteaMirror added the type/question issue/stale labels 2025-11-02 06:33:34 -06:00

GiteaMirror closed this issue

2025-11-02 06:33:34 -06:00

GiteaMirror commented

2025-11-02 06:33:35 -06:00

@lunny commented on GitHub (Jul 7, 2020):

It will not work. Gitea will save repository information on database to display them on web UI.

@lunny commented on GitHub (Jul 7, 2020): It will not work. Gitea will save repository information on database to display them on web UI.

GiteaMirror commented

2025-11-02 06:33:35 -06:00

@kinos9 commented on GitHub (Jul 7, 2020):

It will not work. Gitea will save repository information on database for display them on web UI.

Ok, thanks. And is it possible to exclusively import an existent repository to gitea, forcing gitea to regenerate db information?

Thx

@kinos9 commented on GitHub (Jul 7, 2020): > It will not work. Gitea will save repository information on database for display them on web UI. Ok, thanks. And is it possible to exclusively import an existent repository to gitea, forcing gitea to regenerate db information? Thx

GiteaMirror commented

2025-11-02 06:33:35 -06:00

@lunny commented on GitHub (Jul 7, 2020):

You can do that via git push. and if you enabled automatically create repository when push. It will become more easy.

@lunny commented on GitHub (Jul 7, 2020): You can do that via `git push`. and if you enabled `automatically create repository when push`. It will become more easy.

GiteaMirror commented

2025-11-02 06:33:35 -06:00

@kinos9 commented on GitHub (Jul 7, 2020):

You can do that via git push. and if you enabled automatically create repository when push. It will become more easy.

Ah ok, so I have to change remote and push all the repository content, re-creating a new git repo, and is not possible to directly move the server-side content?

@kinos9 commented on GitHub (Jul 7, 2020): > You can do that via `git push`. and if you enabled `automatically create repository when push`. It will become more easy. Ah ok, so I have to change remote and push all the repository content, re-creating a new git repo, and is not possible to directly move the server-side content?

GiteaMirror commented

2025-11-02 06:33:36 -06:00

@stale[bot] commented on GitHub (Sep 5, 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 (Sep 5, 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.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#5704