{"action":"created","issue":{"url":"https://api.github.com/repos/drush-ops/drush/issues/1320","labels_url":"https://api.github.com/repos/drush-ops/drush/issues/1320/labels{/name}","comments_url":"https://api.github.com/repos/drush-ops/drush/issues/1320/comments","events_url":"https://api.github.com/repos/drush-ops/drush/issues/1320/events","html_url":"https://github.com/drush-ops/drush/issues/1320","id":66164008,"number":1320,"title":"drush pm-update but leave an index file","user":{"login":"drubage","id":2574144,"avatar_url":"https://avatars.githubusercontent.com/u/2574144?v=3","gravatar_id":"","url":"https://api.github.com/users/drubage","html_url":"https://github.com/drubage","followers_url":"https://api.github.com/users/drubage/followers","following_url":"https://api.github.com/users/drubage/following{/other_user}","gists_url":"https://api.github.com/users/drubage/gists{/gist_id}","starred_url":"https://api.github.com/users/drubage/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/drubage/subscriptions","organizations_url":"https://api.github.com/users/drubage/orgs","repos_url":"https://api.github.com/users/drubage/repos","events_url":"https://api.github.com/users/drubage/events{/privacy}","received_events_url":"https://api.github.com/users/drubage/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":10,"created_at":"2015-04-03T15:13:33Z","updated_at":"2015-04-08T19:10:35Z","closed_at":"2015-04-06T16:49:40Z","body":"We have set up some useful scripts that use drush and other command line functions to update several drupal sites on the same server using a single management site. When we drush pm-update drush will make a backup of the entire root directory of the site while it is working. It leaves behind the folder where it downloads Drupal and the sites folder. On our server this results in the directories and files being visible as there is no index file during this time (this is something we can fix but many servers might be configured this way). Also, because the owner of the files from drush updates is always root we need to chown the files/folders to the right account after drush is done. On a big update, however, this can take several minutes and during that time the site will be in 500 error mode (as the .htaccess file has the wrong ownership). We have overcome this issue with a custom 500 error page that shows a \"This website is currently undergoing maintenance. It should back up within a few minutes. Thank you for your patience!\" message so this is not as big of a deal.\r\n\r\nWhat we'd like to be able to do is copy an index.html file in the site root and then run drush updates but have it leave the index.html file in the root so that we can display that same useful error message to our users \"This website is currently undergoing maintenance. It should back up within a few minutes. Thank you for your patience!\". After the drush updates are done we remove that file.\r\n\r\nIs this possible? Like can we tell drush not to backup that index.html file when it updates Drupal? Or are we not doing the drush updates properly? Seems like they will always break a website while they are running.\r\n\r\nThanks!\r\n\r\n-Drew\r\n"},"comment":{"url":"https://api.github.com/repos/drush-ops/drush/issues/comments/91007325","html_url":"https://github.com/drush-ops/drush/issues/1320#issuecomment-91007325","issue_url":"https://api.github.com/repos/drush-ops/drush/issues/1320","id":91007325,"user":{"login":"drubage","id":2574144,"avatar_url":"https://avatars.githubusercontent.com/u/2574144?v=3","gravatar_id":"","url":"https://api.github.com/users/drubage","html_url":"https://github.com/drubage","followers_url":"https://api.github.com/users/drubage/followers","following_url":"https://api.github.com/users/drubage/following{/other_user}","gists_url":"https://api.github.com/users/drubage/gists{/gist_id}","starred_url":"https://api.github.com/users/drubage/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/drubage/subscriptions","organizations_url":"https://api.github.com/users/drubage/orgs","repos_url":"https://api.github.com/users/drubage/repos","events_url":"https://api.github.com/users/drubage/events{/privacy}","received_events_url":"https://api.github.com/users/drubage/received_events","type":"User","site_admin":false},"created_at":"2015-04-08T19:10:35Z","updated_at":"2015-04-08T19:10:35Z","body":"Sorry one more question of clarification. On this point...\r\n\r\nat Pantheon, it is possible to update your dev site, after which you can push your code up from dev to test and live.\r\n\r\nAre you saying at Pantheon customers are required to update their Drupal modules themselves you guys don't manage that for customers?"}}