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

automatic deployment or websites

From: Jamie <jam5t3r_at_gmail.com>
Date: 2006-05-18 02:48:34 CEST

What tools are available for monitoring a repository and updating a
production server when the repository has changed?

I have looked at CruseControl and BuildBot, but these both seem
overkill for my requirements, I do not need a build to take place,
its just a website with php scripts that just need updating into the
live site. I would like to avoid installing java on the server.

My scenario is that I have a development branch, then release
branches, 1.0, 1.1, 1.2 etc... the development site is updated on
every commit so that this is always up to date. I then want to merge
a release (or is if better to delete and copy?) into the staging-dev,
then staging-live, then live branches (tags).

When one of the staging-dev, then staging-live, or live branches is
modified I want it to be automatically deployed to the website root
of the correct site. Everything is run on the same server if that
makes any difference, also the server is linux.

I was thinking of writing a c program like this http://
subversion.tigris.org/faq.html#website-auto-update and running it
every 10 minutes with a cron job, but I am not sure if this would be
too much going on? I don't know how much resources running an update
on 3 repositories every 10 minutes would take. I am already using
this technique on the development site, but its called from a post
commit hook script.

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.

Any advice appreciated

Jamie

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 18 02:49:29 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.