diff options
author | Joey Hess <joeyh@joeyh.name> | 2017-05-11 13:20:23 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2017-05-11 13:20:23 -0400 |
commit | d88ddbf63dbaa64257bfa4905de200c0b3f3d5f1 (patch) | |
tree | 179b60438ee74f662b298fd528ddd869884f27eb | |
parent | b75462f73a007010277f400b7f91f91b9ea3ade2 (diff) |
response
-rw-r--r-- | doc/forum/deploy/comment_1_bd9855cc19f0f49620258564845f1f77._comment | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/forum/deploy/comment_1_bd9855cc19f0f49620258564845f1f77._comment b/doc/forum/deploy/comment_1_bd9855cc19f0f49620258564845f1f77._comment new file mode 100644 index 000000000..1f4732b8d --- /dev/null +++ b/doc/forum/deploy/comment_1_bd9855cc19f0f49620258564845f1f77._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2017-05-11T17:13:35Z" + content=""" +I'm not sure that a bare repository is the best way to go about it. + +One way to do it is to have a non-bare repository, which gets updated when +you push (by eg setting receive.denyNonFastforwards=false), and have that +non-bare repository be the one you push to deploy to. + +While you could push first to a bare repository and have it then push on +the the non-bare repository, that seems to mostly only complicate things, +since you will need to find a way to copy the annexed file contents from +the bare to the non-bare repository. +"""]] |