Quote:
Originally Posted by boinkster
Thanks for your book. It has been most enlightening on managing Drupal projects.
|
Thanks!
Quote:
|
I'm having trouble with SVN and the files directory. Specifically, all the sub dir/files that Drupal creates. Since they are owned by 'nobody', when I run SVN it chokes on them since it doesn't have write permissions, which adds locks and generally buggers up the check out.
|
'nobody' is the user used by the Apache HTTP Server; when you upload a file, it is created by that user.
Basically, in order to include the files sub dir, the user who is going to be doing the "svn add" or "svn commit" or "svn update" needs to have group privileges there.
You can do this, or else set up a cron job or else run a script to change permissions recursively each time you are going to use SVN on that subdir.
Victor Kane
Quote:
Constantly scanning the files dir for new items to chmod doesn't seem practical.
While pouring over your excellent book for clues, I noticed (page 116 figure 5-5) in the Trac log of commits that the 5th commit has the message "moved files directory out of version control"
How do you deal with this? Is keeping the files dir in the repository possible without lots of intervention?
|