Re: what permissions are needed to let a php script call the "svn update" subversion command?
- From: Jake Barnes <lkrubner@xxxxxxxxxxxxx>
- Date: Fri, 12 Dec 2008 01:27:02 -0800 (PST)
On Dec 11, 11:33 pm, gordonb.c8...@xxxxxxxxxxx (Gordon Burditt) wrote:
If I log into my server as root, I can easily run this line:
/usr/bin/svn update /home/www/contentingester --username lkrubner --
password xxxxxxxx
What current working directory is needed to make this work?
But when I put it in a PHP script this does not work (and by that
mean, the command "svn update" seems to never be called):
How do you determine this?
Only that, after calling the PHP script, I can still log into the
server as root and run "svn update" and then see the files copied from
the Subversion repository to the working copy on the server. And that
is with no additional files having been committed to the repository in
the mean time.
A typical test I run:
1.) make a change to a file
2.) commit it to Subversion
3.) run PHP script
4.) log into server as root and run "svn update"
If the "svn update" command had run in #3, then there would be no
files to update in #4. But there are.
.
- References:
- Prev by Date: Re: what permissions are needed to let a php script call the "svn update" subversion command?
- Next by Date: Re: How can I detect remote socket close when I use an epoll programming style?
- Previous by thread: Re: what permissions are needed to let a php script call the "svn update" subversion command?
- Next by thread: Re: what permissions are needed to let a php script call the "svn update" subversion command?
- Index(es):
Relevant Pages
|