You have code on a production server that does not allow Drush to be running and you do not enjoy the idea of copying over live files. If these sites are already tracking a git repository that is great, simply do a push and pull and you are done. It gets more complicated though if the repositories are woefully out of sync or if they have never had a git repository configured.<\/p>\n
The solution I devised allows you to update the site locally, make a nice commit, and then fetch it on the remote server and reset the filesystem to the fetch that was just made. Here are the steps:<\/p>\n
$git init<\/pre>\n<\/li>\n
$drush pm-update drupal<\/pre>\n<\/li>\n
$git add -u\r\n$git commit -m\"Upgrade to Drupal version x.yz\"<\/pre>\n<\/li>\n
$git remote add origin RemoteRepositoryURL\r\n$git push origin master<\/pre>\n<\/li>\n
$git init\r\n$git remote add origin RemoteRepositoryURL\r\n$git fetch --all\r\n$git reset --hard origin\/master<\/pre>\n<\/li>\n
I know the above is quite unorthodox. You also need to be careful as it will only rebuild the files you are tracking. I do not normally advocate for tracking entire Drupal installs but if you are in a situation as detailed above, it may be one of the few ways to have a sane update mechanism. For working with remotes I find the git-scm reference pages<\/a> very handy.<\/p>\n","protected":false},"excerpt":{"rendered":" Problem: You have code on a production server that does not allow Drush to be running and you do not enjoy the idea of copying over live files. If these sites are already tracking a git repository that is great, simply do a push and pull and you are done. It gets more complicated though … Continue reading How-to: Use git to update Drupal when you can’t use Drush<\/span>