[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: automatic deployment or websites

From: Russ <rsivak_at_istandfor.com>
Date: 2006-05-18 13:30:55 CEST

If your repo server is the same server as the web server, could you not just use a post commit hook to do the update? And if it is a different server, perhaps the post commit hook can run a remote shell to the web server through ssh and execute svn update?
Sent wirelessly via BlackBerry from T-Mobile.

-----Original Message-----
From: Bronto <bronto@csd-bes.net>
Date: Wed, 17 May 2006 20:52:05
Subject: Re: automatic deployment or websites

My needs are identical to yours and the advice below is what I do,
except I ssh in and svn update manually. I have as a low priority task
(that I'll probably never get to) to write a php script that exec()'s
svn that I'll protect with an .htaccess file so that I can skip the ssh.
  It may not seem to be a big deal, but I have other "devs" (I use the
term loosely) that occasionally commit changes, and ssh and a command
line are beyond them. It would be nice to be able to send them to a
URL, login and click in a link.

 From time to time I've looked for an "svn web client" that has
checkout/update control, but haven't found anything that will work with
apache 1.3x and php4.

If you want to write something to do this automatically, I'd love to
have a copy.

Come to think of it, maybe we can just cron svn update?


Mark Phippard wrote:
> Jamie <jam5t3r@gmail.com> wrote on 05/17/2006 08:48:34 PM:
>> What tools are available for monitoring a repository and updating a
>> production server when the repository has changed?
>> I'm looking for the most simple solution with the least overhead, I'm
>> already worried about the server not being able to handle the load
>> but the client does not want to pay for 2 servers.
> The easiest thing to do is to use svn checkout to turn your web site into
> a normal working copy. Then you just need to run the svn update command
> to deploy changes. In most cases, you could just run a process once a
> night, or every hour, that runs the svn update command. If there are
> updates, they will be pulled down.
> Mark
> _____________________________________________________________________________
> Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
> _____________________________________________________________________________
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 18 13:30:55 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.