On Apr 26, 2007, at 17:05, Brad Rhoads wrote:
> On 4/26/07, Jamie Jackson wrote:
>
>> We've got the SVN repo on linux/Apache but the working copy (a Web
>> site) lives on Win/IIS.
>>
>> Is there a way to arrange a post-commit hook to auto-update the live
>> site via a post-commit with this environment combination?
>
> You could turn on auto autoversioning and then mount the repository
> with webdrive or netdrive and then create the virtual host from
> there. The updates would be automatic.
>
> I've gotten this to work with webdrive. Download it from http://
> www.webdrive.com/products/webdrive/index.html. After the install,
> add a new site with the url, server type WebDav. Click Properties|
> HTTP Settings and disable (uncheck) "Enable persistent connections
> (Keep-Alive). After you have a connection, open the Program
> Settings|Cach Settings|Options and select Custom, Cache Files and
> check all options. Set all boxes to 10 seconds.
>
> Someone else said that netdrive (it's free) works for autoveroning.
> But you might run into trouble trying to get IIS to recognize it.
> It took a lot of work with the vendor to get webdrive to work with
> IIS.
>
> Just do a search of the archive and you'll find several discussions
> about this.
Using an autoversioning webdav mount as the web server's document
root sounds like a bad idea. The performance would be awful.
Jamie's on the right track, having a working copy on the web server.
Now you just need a way to update it when a commit takes place. If
this were Unix / Linux / Mac OS X, I would write a post-commit hook
on the repository server which did something like "ssh user@webserver
svn update /path/to/workingcopy". This would cause the repository
server to connect to the web server over ssh and run svn update on
the working copy. Since your server is Windows, you may be able to
get the same thing to work if you install Cygwin, though I can't help
you further with that as I don't use Windows.
If that doesn't work, perhaps it's sufficient if the web server just
runs "svn update" periodically -- be it every 5 minutes or every hour
or every day, depending on your needs. Again, if this were a Unix-
like OS, I would schedule this on the web server via cron. On
Windows, I'm sure there's a similar way to schedule tasks to run at a
particular time.
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 27 00:33:22 2007