repository root path to be in different server #3963

New Issue

GiteaMirror · 2025-11-02T05:31:59-06:00

GiteaMirror commented

2025-11-02 05:31:59 -06:00

Originally created by @zuhairamahdi on GitHub (Sep 16, 2019).

Gitea version (or commit ref):
Git version:
Operating system:
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

Hello,
I'm trying to move the repositories to a different server that we have other than the server where gitea.

we tried to change the ROOT in app.ini but it is with no use.

can anyone help with this issue?

Screenshots

Originally created by @zuhairamahdi on GitHub (Sep 16, 2019).   - Gitea version (or commit ref): - Git version: - Operating system: - 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 Hello, I'm trying to move the repositories to a different server that we have other than the server where gitea. we tried to change the `ROOT` in `app.ini` but it is with no use. can anyone help with this issue? ## Screenshots

GiteaMirror added the issue/needs-feedback label 2025-11-02 05:31:59 -06:00

GiteaMirror closed this issue

2025-11-02 05:31:59 -06:00

GiteaMirror commented

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

@lunny commented on GitHub (Sep 17, 2019):

How did you change that option?

@lunny commented on GitHub (Sep 17, 2019): How did you change that option?

GiteaMirror commented

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

@zuhairamahdi commented on GitHub (Sep 17, 2019):

@lunny I tried in multiple ways. first was using the full path as if I was accessing through the file explorer:
\\<server-ip-here>\c$\gitea\gitea-repositories
secondly I tried to map the server to a local drive (I called G:\). all of these methods gave me an error stating the no file or directory exist.

@zuhairamahdi commented on GitHub (Sep 17, 2019): @lunny I tried in multiple ways. first was using the full path as if I was accessing through the file explorer: `\\<server-ip-here>\c$\gitea\gitea-repositories` secondly I tried to map the server to a local drive (I called `G:\`). all of these methods gave me an error stating the no file or directory exist.

GiteaMirror commented

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

@lunny commented on GitHub (Sep 17, 2019):

I think only local path is supported there.

@lunny commented on GitHub (Sep 17, 2019): I think only local path is supported there.

GiteaMirror commented

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

@guillep2k commented on GitHub (Sep 17, 2019):

@lunny I tried in multiple ways. first was using the full path as if I was accessing through the file explorer:
\\<server-ip-here>\c$\gitea\gitea-repositories
secondly I tried to map the server to a local drive (I called G:\). all of these methods gave me an error stating the no file or directory exist.

@zuhairamahdi In Windows, network drives like G:\ are specific to each user. For example, if you log in as "Administrator" and create G:\ from a network path, services and other processes running with different credentials (SYSTEM, NETWORK SERVICE, LOCAL SERVICE, etc.) will not be able to see it. Even so, they won't unless they load the user profile (I don't know if that's the default for services). Finally, network drives can be "permanent" or "temporary"; the latter disappear when you log off.

Anyway, I'm not sure using a network path for repositories is advisable (file locks can be tricky).

@guillep2k commented on GitHub (Sep 17, 2019): > > > @lunny I tried in multiple ways. first was using the full path as if I was accessing through the file explorer: > `\\<server-ip-here>\c$\gitea\gitea-repositories` > secondly I tried to map the server to a local drive (I called `G:\`). all of these methods gave me an error stating the no file or directory exist. @zuhairamahdi In Windows, network drives like `G:\` are specific to each user. For example, if you log in as "Administrator" and create `G:\` from a network path, services and other processes running with different credentials (`SYSTEM`, `NETWORK SERVICE`, `LOCAL SERVICE`, etc.) will not be able to see it. Even so, they won't unless they load the user profile (I don't know if that's the default for services). Finally, network drives can be "permanent" or "temporary"; the latter disappear when you log off. Anyway, I'm not sure using a network path for repositories is advisable (file locks can be tricky).

GiteaMirror referenced this issue

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

[PR #3964] [MERGED] api: repos/search: add parameters to control the sort order #17169

GiteaMirror referenced this issue

2025-11-02 13:20:31 -06:00

[PR #4599] [MERGED] dashboard: sort Repositories widget by most recently updated (issue #3963) #17430

Sign in to join this conversation.