Capistrano isn't responsible for setting executable bits on your files. If you're using subversion, you can make sure the files are marked as executable in your repository, and then they'll be made executable automatically on check-out. Google for the svn:executable property to see how that works.

- Jamis

On Jan 1, 2008, at 8:09 PM, hnchuong wrote:


Hi all,

My Capistrano deployment failed when Capistrano need to start the
server, because scripts in /script folder doesn't have executable
permission. Therefore in my recipe, i need to have a
"after_update_code" task to set the permission of scripts in scripts
folder to be executable.

I wonder why i need to do this, as I think this should be default be
Capistrano. Could anyone explain?

Thanks
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to