documentation updates for new receive.denyCurrentBranch=updateInstead support
This commit was sponsored by andrea rota.
This commit is contained in:
parent
e6857e75a6
commit
a700fdf5cf
9 changed files with 59 additions and 45 deletions
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 4"""
|
||||
date="2017-02-17T19:34:55Z"
|
||||
content="""
|
||||
An easier way to set this up is available now, see
|
||||
<https://git-annex.branchable.com/tips/making_a_remote_repo_update_when_changes_are_pushed_to_it/>
|
||||
"""]]
|
|
@ -7,4 +7,8 @@
|
|||
This is not something the assistant really handles yet. The issue is that if you have a non-bare repository on the USB drive, something has to run `git annex sync` in it when changes are pushed to it, to update it to display the files that are in the repository.
|
||||
|
||||
One way to do this is to set up a non-bare repository by hand and add a git post-receive hook that runs `git annex sync`
|
||||
|
||||
Update: Another way, recently added is
|
||||
<https://git-annex.branchable.com/making_a_remote_repo_update_when_changes_are_pushed_to_it/>
|
||||
This new approach even supports FAT filesystems!
|
||||
"""]]
|
||||
|
|
|
@ -6,5 +6,7 @@
|
|||
content="""
|
||||
Sure you can.. That's how <http://downloads.kitenet.net/> works, which is where people download git-annex builds from!
|
||||
|
||||
[[tips/making_a_remote_repo_update_when_changes_are_pushed_to_it]]
|
||||
|
||||
[[tips/setup_a_public_repository_on_a_web_site]]
|
||||
"""]]
|
||||
|
|
|
@ -0,0 +1,13 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 4"""
|
||||
date="2017-02-17T19:38:45Z"
|
||||
content="""
|
||||
It's now pretty easy to set up a remote on a USB drive so that `git annex
|
||||
sync` will update the work tree. See
|
||||
<https://git-annex.branchable.com/tips/making_a_remote_repo_update_when_changes_are_pushed_to_it/>
|
||||
|
||||
However, the assistant does not do this by default when adding repos on USB
|
||||
drives, due to the likely confusion that setting up such a repo would
|
||||
cause, as described in my previous comment.
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue