Support for multiple different repo root dirs #10866

New Issue

GiteaMirror · 2025-11-02T09:20:28-06:00

GiteaMirror commented

2025-11-02 09:20:28 -06:00

Originally created by @csillag on GitHub (May 18, 2023).

Feature Description

Different repositories might have different storage requirements. (speed, size, etc.)
You might want to put some data on SSD, something on HDD, something on RAID, or a combination of the above, etc.

It would be great if one could specify multiple different data ROOT directories, and when creating a new repo (from the web UI or via the API), one could optionally specify which data directory to use for storing the files for this specific new repo.

Screenshots

No response

Originally created by @csillag on GitHub (May 18, 2023). ### Feature Description Different repositories might have different storage requirements. (speed, size, etc.) You might want to put some data on SSD, something on HDD, something on RAID, or a combination of the above, etc. It would be great if one could specify multiple different data ROOT directories, and when creating a new repo (from the web UI or via the API), one could optionally specify which data directory to use for storing the files for this specific new repo. ### Screenshots _No response_

GiteaMirror added the type/proposal type/feature labels 2025-11-02 09:20:28 -06:00

GiteaMirror commented

2025-11-02 09:20:29 -06:00

@csillag commented on GitHub (May 18, 2023):

Currently, the only way to achieve this (storing the data files on different devices) is to run multiple instances of gitea, but then the different repositories must be accessed using different URLs. Ideally, the storage options of a given repo should be an internal setting of that repo, and not influence the URL.

@csillag commented on GitHub (May 18, 2023): Currently, the only way to achieve this (storing the data files on different devices) is to run multiple instances of gitea, but then the different repositories must be accessed using different URLs. Ideally, the storage options of a given repo should be an internal setting of that repo, and not influence the URL.

GiteaMirror commented

2025-11-02 09:20:29 -06:00

@lunny commented on GitHub (May 18, 2023):

Ah, yes. #22775 could be the first step towards the requirement.

@lunny commented on GitHub (May 18, 2023): Ah, yes. #22775 could be the first step towards the requirement.

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#10866