Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Per-repository storage of LFS objects (optional) #613

Open
jaw opened this issue Dec 5, 2024 · 2 comments
Open

Per-repository storage of LFS objects (optional) #613

jaw opened this issue Dec 5, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@jaw
Copy link
Contributor

jaw commented Dec 5, 2024

I would like to have an option to create one LFS object storage per repository instead of just one for all repos which is currently the case.

Since soft serve already has a easy-to-understand file system structure, adding this would allow for inspecting and reasoning around disk usage and backup strategies for a sysadmin.

It would allow for easier moving large repos between instances of soft-serve on a file system level also.

As this would require quite a lot of migration code which is difficult to test, a reasonable concession would then be to offer this as an option when the server is created.

@aymanbagabas aymanbagabas added the enhancement New feature or request label Dec 5, 2024
@jaw
Copy link
Contributor Author

jaw commented Dec 6, 2024

@aymanbagabas I'd be open to working on this next as it's something I want if it at all has a chance to go through.

@aymanbagabas
Copy link
Member

@aymanbagabas I'd be open to working on this next as it's something I want if it at all has a chance to go through.

Soft Serve currently does store each repo's LFS object in its own directory under $SOFT_SERVE_DATA/lfs. Each directory represents the repository id. Then, each LFS object follows the following structure objects/{OID[0:2]/OID[2:4]/OID}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants