xforty / capistrano-drush-make Goto Github PK

capistrano-ash sets some permissions that fail after a second run.

Might need to override the task to skip the backups.

 ** [out :: rsc-prod01.xforty.com] ./20120214145451/install.php
    command finished in 7299ms
  * Removing the tempory copy
  * executing "rm -rf /tmp/20120214145451"
    servers: ["rsc-prod01.xforty.com"]
    [rsc-prod01.xforty.com] executing command
 ** [out :: rsc-prod01.xforty.com] rm: cannot remove `/tmp/20120214145451/sites/adamwpearce/settings.php': Permission denied
 ** [out :: rsc-prod01.xforty.com] rm: cannot remove directory `/tmp/20120214145451/sites/adamwpearce/themes': Permission denied
 ** [out :: rsc-prod01.xforty.com] rm: cannot remove directory `/tmp/20120214145451/sites/adamwpearce/files': Permission denied
 ** [out :: rsc-prod01.xforty.com] rm: cannot remove `/tmp/20120214145451/sites/default/settings.php': Permission denied
 ** [out :: rsc-prod01.xforty.com] rm: cannot remove directory `/tmp/20120214145451/sites/default/themes': Permission denied
 ** [out :: rsc-prod01.xforty.com] rm: cannot remove directory `/tmp/20120214145451/sites/default/files': Permission denied

There is a lot of automation missing from this process. For example if a server has database updates that need to be applied it should apply them. If it fails it should roll them back. It should put the server in maintenance mode. It would be nice to get a solid set of automation for drush make deployments. Let's document the requirements here.

** [out :: rsc-prod01.xforty.com] query: SELECT COUNT(pid) FROM url_alias database.mysql.inc:135
** [out :: rsc-prod01.xforty.com] Table 'xforty.system' doesn't [error]
** [out :: rsc-prod01.xforty.com] exist

Not sure what to do to handle this. But the initial cap deploy causes drush clear cache to fail.

Should check to see if it is defined. If it isn't just ignore it.

/home/pearcec/.rvm/gems/ruby-1.9.2-p290/gems/capistrano-2.9.0/lib/capistrano/configuration/namespaces.rb:188:in method_missing': undefined local variable or methoddefault_multisite' for #Capistrano::Configuration::Namespaces::Namespace:0x00000002b9f580 (NameError)

A backup gets created an put in the DocumentRoot. Every time you run cap deploy after a failed attempt it keep rolling in the prior backup. This seems sloppy. Seems capistrano-ash isn't well though through on the issue of managing backups.