Thanks Jamis. That makes sense. I'll give it a go. Mark.
On Sep 4, 5:51 pm, Jamis Buck <[EMAIL PROTECTED]> wrote: > It's because copy deploys to your windows machine, and then copies the > files to the remote server. The problem is that windows has no notion > of "executable", so the deploy to windows ignores that flag. > > You're going to need to add an after hook on deploy:update_code that > does a chmod +x on the files you want to be executable. > > - Jamis, waving (once more) a frustrated fist in the air at Microsoft > generally and Windows specifically > > On Sep 4, 2008, at 4:42 PM, MarkMT wrote: > > > > > Hi, very new to Capistrano and slowly inching towards deployment of my > > test Rails app. I think I'm getting close, but the issue I have right > > now is that the scripts are ending up on the deployment machine > > without execute permission. I'm deploying from a local svn repository > > on a Windows machine using :copy. I've set svn:executable from both > > tortoiseSVN and command line, and it seems ok, but when I do > > deploy:update, the files end up on the target machine still with no > > execute permission. > > > Any clues? > > > > > > > smime.p7s > 3KViewDownload --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
