No need for mkdir, make it simpler
This commit is contained in:
parent
a251762c7c
commit
8d8d6a58d7
1 changed files with 2 additions and 5 deletions
|
@ -24,16 +24,13 @@ as non-bare repositories. Except for these caveats:
|
||||||
Here is a quick example of how to set this up, using `origin` as the remote name, and assuming `~/annex` contains an annex:
|
Here is a quick example of how to set this up, using `origin` as the remote name, and assuming `~/annex` contains an annex:
|
||||||
|
|
||||||
On the server:
|
On the server:
|
||||||
|
git init --bare bare-annex.git
|
||||||
mkdir bare-annex
|
|
||||||
cd bare-annex
|
|
||||||
git init --bare
|
|
||||||
git annex init origin
|
git annex init origin
|
||||||
|
|
||||||
Now configure the remote and do the initial push:
|
Now configure the remote and do the initial push:
|
||||||
|
|
||||||
cd ~/annex
|
cd ~/annex
|
||||||
git remote add origin example.com:bare-annex
|
git remote add origin example.com:bare-annex.git
|
||||||
git push origin master git-annex
|
git push origin master git-annex
|
||||||
|
|
||||||
Now `git annex status` should show the configured bare remote. If it does not, you may have to pull from the remote first (older versions of `git-annex`)
|
Now `git annex status` should show the configured bare remote. If it does not, you may have to pull from the remote first (older versions of `git-annex`)
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue