Hi guys, this causes deploy to not make assumptions about folders
existing and makes it less brittle on some scms (including mercurial).
Please put it into trunk :)
--Matt
--
Matthew Elder
Junior Engineer, Tackle Technology
http://tackletechnology.org/
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
diff -r 19a5b1d7cb6c -r d0d383dbd4cb lib/capistrano/recipes/deploy.rb
--- a/lib/capistrano/recipes/deploy.rb Thu May 31 13:07:33 2007 -0700
+++ b/lib/capistrano/recipes/deploy.rb Thu May 31 13:19:43 2007 -0700
@@ -147,8 +147,12 @@ namespace :deploy do
task :finalize_update, :except => { :no_release => true } do
run "chmod -R g+w #{release_path}" if fetch(:group_writable, true)
+ # mkdir -p is making sure that the directories are there for some SCM's that don't
+ # save empty folders
run <<-CMD
rm -rf #{release_path}/log #{release_path}/public/system #{release_path}/tmp/pids &&
+ mkdir -p #{release_path}/public &&
+ mkdir -p #{release_path}/tmp &&
ln -s #{shared_path}/log #{release_path}/log &&
ln -s #{shared_path}/system #{release_path}/public/system &&
ln -s #{shared_path}/pids #{release_path}/tmp/pids
