They are two different approaches to the same problem, and they each have advantages. Git-media and git-annex are extensions to Git meant to manage large files. Thus, the need for a system to manage the data that requires little to no maintenance. Git Large File Storage (LFS) is an open source project from GitHub that began life as a fork of git-media. Since the group is focused on physics research, other people that come after I leave may not have the necessary skills for maintaining the server. On the other hand, I am a post-doc and may need to leave the group at any moment in favor of a permanent position. We do not deal with personal information and leaks or data loss would have only minor consequences. However, the data stored does not contain sensitive information. Ideally, I should be able to even read the data from within the server with the service running, since we may do some data analysis inside this computer.Ĭomment about point 2: I know not performing regular updates may leave security holes. it will not be compacted in a binary blob where you need the server running to retrieve it. In the case it breaks, will the data be stored in a way someone can easily retrieve, i.e.setup once and, as long no one updates the OS, it should not break (see comment below). If I must deploy GitLab's CE, how hard is to maintain such a server? My ideal scenario is a zero maintenance, i.e.Basically I published a git repo where there are large files (30 and 150 mb) and I have been uploading those with git lfs. Is that the only way? Ideally, I would like to be able to tell GitLab that our files are stored elsewhere, and the git repo just point out that "elsewhere" is our storage server? Not sure if this is the right place to ask but I have the following question. The solution seems to be for us to deploy the community edition of GitLab on our storage server. However, this seems that it will upload the files to GitLab's server, defeating the whole purpose of a storage computer (also, we would need to buy storage from them). So, it would make sense to create a "data" repository where most of the files will be binary ones, stored and tracked via lfs. You install the extension and set the file types you want to use. We already use GitLab (the cloud version) to version control our codes and easily share them between us. Git LFS allows you to utilize several servers. When researching the best way to do this, I came across git lfs. As such, I needed to think the best way to organize the data we will be generating. I am part of a small physics research team (10-15 people) which recently has acquired a storage server and I will be responsible for setting it up.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |