Hi,
I tried using Git LFS with SCM Manager and noticed that LFS files are stored inside the repository as .blob files within the \store\blob folder. Is that correct?
I would like to know if there is a way to configure the storage path for LFS files, potentially pointing to a different machine than the one where the repository is stored.
I searched through various posts about the interaction between SCM Manager and Git LFS but couldn’t find an answer to my question.
Thanks in advance!
Hi @paolongit ,
what you’ve figured out is correct, that’s the way SCM-Manager handles LFS files internally. Currently, there is no way to store the files elsewhere. You can move the whole repository folder though, if this might help (using the custom storage plugin. May I ask for the reason why you want to store the files somewhere else?
Hi,
thank you for your response. I’d like to create a simple way to store the “artifacts” in a dedicated storage area (such as a NAS or a Nexus framework). While I could configure each local git repository individually (using git config -f .lfsconfig ...), it would be more efficient to manage this centrally by delegating the redirection to the remote repository manager (SCM Manager).
Paolo
Ah okay, I think I get it. Our goal is to keep all repository related data in one place. Would it be possible for you to use links for the lfs directory to “relocate” the files?
Hi, and thank you again.
I’m not sure I understood what you mean. Do you mean mapping the \store\blob\git-lfs directory as a link on the remote repository managed by SCM Manager?
If so, the problem would be that I would need to perform this operation for each remote repository. I would prefer a centralized solution that requires less effort and fewer manual operations.
Hi,
yes, that was my idea. Clearly you are right that this is not optimal if you have to manage multiple repositories or whenever repositories are created relatively often.
To solve your problem, I could imagine a small plugin where you can specify the location for blob stores individually, similar to the repository location plugin. Or one could extend the functionality of this plugin.
If you like, we can gladly provide an offer for the implementation of the plugin. Alternatively, you can submit a pull request for your own development in the SCM Manager’s GitHub repository, and we will support you in the implementation and conduct a review.