This is not an exposed site and is strictly used for production....
Sounds like I have two choices:
1. svn export file:///var/production_repo/trunk/ /var/httpd
- production server command?
2. svn update file:///var/production_repo/trunk/ /var/httpd
- little less secure but okay for development?
Is #2 the right command for abstracting all the information to the apache
directory?
Also, all the code is PHP5 stuff with Smarty templates and what not. The
paths are correct and even configurable wherever they are put.
- rob
> -----Original Message-----
> From: Gavin Lambert [mailto:gavinl@compacsort.com]
> Sent: Tuesday, July 11, 2006 9:19 PM
> To: 'Robert Sandie'
> Cc: users@subversion.tigris.org
> Subject: RE: SVN Hook specifically for Trunk Question
>
> Quoth Robert Sandie <mailto:sandieman@gmail.com>:
> > Very basic.. I know, I know!
> >
> > Am trying to hook the trunk instead of the entire source repository.
> >
> > Currently in post-commit:
> > svn update /var/httpd/
> >
> > How would I change it to just transfer over the /trunk/
> > directory and make that the /var/httpd/ directory?
>
> You just need to make sure that whatever you had checked out to the
> /var/httpd folder in the first place was the correct path.
>
> Don't forget to make sure your server won't serve anything from the .svn
> folders, though, otherwise you'll have a security hole. If you want to
> be safe, then you should export to the folder rather than checking out
> (but then you won't be able to update later, so your post-commits will
> take longer). You could svn export to a third folder and then sync that
> to /var/httpd....
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 12 03:36:44 2006