summaryrefslogtreecommitdiff
path: root/doc/bugs/assistant_does_not_allow_adding_an_existing_repo/comment_2_55fcf44eefe6abac3f61a14e9ce9206c._comment
blob: 8ebdb4ff98cb5b21817899c6a47e1060bbd77409 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
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.
"""]]