Closed ghost closed 10 years ago
No, the server doesn't even have to have git installed. This is a one way sync from local (or where ever dploy
is) to the server.
The thought-process behind it is you shouldn't really be editing files directly on the server, so it works fine in most cases, and works in just about any environment cuz pretty much everywhere has at least FTP.
There are exceptions to this rule, though, such as CMS' that upload files and maybe you need to have those files in the repo. As far as I know, dploy
is not build to handle that; you might be better off having Git on the server.
As for how dploy
works: creates a .rev
(revision) file that contains the commit hash of the last updated commit on the server. dploy
compares the revision from the server with the revision locally, finds out what files have changed since that revision, uploads just the files that have changed and updates the .rev
file.
Awesome, thanks for the info!
This is just a question rather than an issue.
Does dploy require that the server be a git repository also? Typically I run git locally only and just files up via ftp. How does the dploy compare the local and remote versions?
Thanks!