mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment: Strategy for getting up and running

Browse source
This commit is contained in:
effigies 2015-03-09 17:32:19 +00:00 • committed by admin
parent 50d85ecefb
commit 34cea08340
1 changed files with 34 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

34
doc/bugs/assistant_does_not_allow_adding_an_existing_repo/comment_2_55fcf44eefe6abac3f61a14e9ce9206c._comment Normal file
View file

@ -0,0 +1,34 @@
[[!comment format=mdwn
username="effigies"
subject="Strategy for getting up and running"
date="2015-03-09T17:32:19Z"
content="""
The following is the set of steps I use when setting assistant up on a new repository:
git clone user@host:repo.git
pushd repo
git annex init
touch EMPTY
git annex add EMPTY
git commit -m 'Initial commit'
git push --all
git annex copy --to origin
git annex direct
git annex sync
git annex untrust .
popd
Entering the folder path now lets the assistant take over.
For an existing repository:
git clone user@host:repo.git
pushd repo
git annex get .
git annex direct
git annex sync
git annex untrust .
popd
Not sure if this would be helpful for working out what the assistant behavior should be, but maybe it'll help others get to the point where the assistant works with a gitolite managed repo.
"""]]