Hi When a specific commit is deployed and runs on a server, I think it is useful to keep .git subdirectory with it.
Why? 1) Having the git repo with the correct HEAD allows to run `git status`, for example, and quickly inspect the working copy for any possible changes or additions. 2) The other possible use is lightning-fast updates (for simpler cases, where atomicity is not important) using git 2.3's "push to deploy" feature (see https://github.com/blog/1957-git-2-3-has-been-released). The working tree files will be updated automatically. Can anybody suggest how to achieve this with Capistrano 3, without hacking it too much? Of course, I know that it is a good practice to always make a proper release, in its own directory. However, there are times when it is vital to fix a production problem very quickly. Or times when you want to preview numerous small updates at a staging server in quick succession. I tried running `git --git-dir=<my project>/repo --work-tree=<my project>/current status`. Strangely, git shows every file as deleted and untracked in that case. (Using Capistrano 3.3.5, git 2.3.1.167). Best regards --- Yar -- You received this message because you are subscribed to the Google Groups "Capistrano" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/88b8f83b-aff9-474b-87da-2f204415808d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
