Is git-annex appropriate for my scenario?
Posted
by
Karel Bílek
on Super User
See other posts from Super User
or by Karel Bílek
Published on 2012-11-15T10:29:25Z
Indexed on
2012/11/15
11:08 UTC
Read the original article
Hit count: 263
git
I have a git repository with source codes I want to put in the open on github.
However, I also have gigabytes of data that I don't want to have in the open and in the repo - they are big, they are proprietary, they are "burdened" with copyrights and so on. However, those are also logically "part of the same project" and I wish to have some control over their history (basically, what git already does).
Right now, I have them in the directory "data" in the repository and I have the directory ignored and I resign on getting them to git.
However, I have read about git-annex and it seems it can do what I want. So, I have two questions.
- Is git annex appropriate for me?
How exactly should I use git annex for my scenario? Meaning - which commands should I use and how?
I have tried to read the official documentation but it talks about use cases that I don't care about. I have the data on one computer only and I don't think I will be moving them soon (it's nice to have the possibility, but it's not why I want to use git annex). Also, the documentation is pretty hard to read.
© Super User or respective owner