diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawl9J51AO9t75xN5k0sJgg8taUo4y0a4hpQ <Daniel@web> | 2013-05-31 21:06:58 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-05-31 21:06:58 +0000 |
| commit | 3ac9b3270c4c1a3f0b902c7fc8835aa240c781f2 (patch) | |
| tree | 0011948a96623e0b075e2c6a1f784d24ccd51e93 | |
| parent | 628946c317bd60f2068782eadf5774f987f7a13d (diff) | |
Running git-annex on top of existing repo
| -rw-r--r-- | doc/forum/help_running_git-annex_on_top_of_existing_repo.mdwn | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/forum/help_running_git-annex_on_top_of_existing_repo.mdwn b/doc/forum/help_running_git-annex_on_top_of_existing_repo.mdwn new file mode 100644 index 000000000..365ad71db --- /dev/null +++ b/doc/forum/help_running_git-annex_on_top_of_existing_repo.mdwn @@ -0,0 +1,12 @@ +## Question +Can git-annex run passively with an existing repo? + +## Scenario +We have an existing web application with large binary assets spread throughout modules in the repo. The project is in constant development with weekly deploys to production and there are many developers working on the project. + +## Goal +We need to maintain the directory structure for these assets without actually committing large binaries to the main remote (hosted on GitHub). I need a solution that has a low barrier of entry when on-boarding new developers. I was thinking maybe a script the is executed on every commit that would filter binaries files based on extensions and commit them to the git-annex remote instead. We are flexible on the type of remote storage type (SSH, S3, etc) + +## Notes +I have gone through the last couple months of forum posts and done a bit of Googling but have come up empty. If anyone can point me in the right direction that would be great. +Thanks! |