diff options
| -rw-r--r-- | doc/forum/how_do_automated_upgrades_work__63__/comment_1_cfd00ac3a3eaa3c2a1d430f6544c32f0._comment | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/forum/how_do_automated_upgrades_work__63__/comment_1_cfd00ac3a3eaa3c2a1d430f6544c32f0._comment b/doc/forum/how_do_automated_upgrades_work__63__/comment_1_cfd00ac3a3eaa3c2a1d430f6544c32f0._comment new file mode 100644 index 000000000..7269a2a19 --- /dev/null +++ b/doc/forum/how_do_automated_upgrades_work__63__/comment_1_cfd00ac3a3eaa3c2a1d430f6544c32f0._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-06-02T18:57:43Z" + content=""" +The assistant checks for available upgrades a few times a day. +By default, it only pops up a message in the webapp with an upgrade button. + +annex.autoupgrade can configure this, so the assistant can be made +to upgrade without confirmation if you want. + +The upgrade process needs to move the git-annex.linux directory out of the +way and replace it with a new one from the tarball, so it will only +work if the user running the assistant can write to it. +"""]] |