summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar effigies <effigies@web>2015-03-09 17:32:19 +0000
committerGravatar admin <admin@branchable.com>2015-03-09 17:32:19 +0000
commitcd4f71ffba097fe20d19a8b69ce0e0597cebf443 (patch)
treed569bd463ce07270fbe4eab8a737fd313c903456
parentc2b5422d84ee7a81eff70331089385e78b8b0340 (diff)
Added a comment: Strategy for getting up and running
-rw-r--r--doc/bugs/assistant_does_not_allow_adding_an_existing_repo/comment_2_55fcf44eefe6abac3f61a14e9ce9206c._comment34
1 files changed, 34 insertions, 0 deletions
diff --git a/doc/bugs/assistant_does_not_allow_adding_an_existing_repo/comment_2_55fcf44eefe6abac3f61a14e9ce9206c._comment b/doc/bugs/assistant_does_not_allow_adding_an_existing_repo/comment_2_55fcf44eefe6abac3f61a14e9ce9206c._comment
new file mode 100644
index 000000000..8ebdb4ff9
--- /dev/null
+++ b/doc/bugs/assistant_does_not_allow_adding_an_existing_repo/comment_2_55fcf44eefe6abac3f61a14e9ce9206c._comment
@@ -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.
+"""]]