Executable bits when importing a project from a *nix filesystem are preserved with newer versions of Subversion. However, on a Debian deployment machine (svn 1.1.4) I've noticed that executable bits are lost on checkout. I've set up a Capistrano callback to deal with that.
You are either on Windows or deploying to a machine with older version of svn. Use Jamis' advice. -M On Jan 2, 2008 4:08 PM, Jamis Buck <[EMAIL PROTECTED]> wrote: > 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 -~----------~----~----~----~------~----~------~--~---
