<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>[pmwiki-users] Re: How to 'automatically' keep a deployed PmWiki install up to date?</TITLE>
</HEAD>
<BODY>
<DIV dir=ltr><FONT size=2>On Fri, 23 Sep 2005, Crisp, Steve [UK]
wrote:<BR><BR>>> <A
href="http://www.pmwiki.org/wiki/Cookbook/InstallationTracking">http://www.pmwiki.org/wiki/Cookbook/InstallationTracking</A><BR>>> <BR>>>
Let me know your thoughts,<BR><BR><FONT face=Tahoma>On Sun 25/09/2005 08:52,
</FONT><FONT face="Times New Roman">Christian Ridderström
wrote:</FONT></FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>>Have you thought of using CVS to simply update the
installation?<BR>><BR>>This is what I do for my pmwiki installations.
There is no guarantee<BR>>though that a new release of pmwiki won't break old
recipes etc, so I'm<BR>>not sure this is something you'd really like to do
automatically...<BR>><BR>>You should also consider wiki farms/fields in
this context... that should<BR>>reduce the n:o installations you need to
update to one per server.<BR></FONT></DIV>
<DIV dir=ltr><FONT size=2>Use of CVS is a good idea for the repository and
transport mechanism perhaps with a more 'intelligent' front end comparing
what you have installed and what versions are available. Usually you would
not want to checkout from a CVS branch but the static revision tag of a
component indicating it's release. As you say, on a branch and you can not
be sure what you're getting.</FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>Going down the CVS route, I think each PmWiki plug-in
would need to include a common named file e.g. ReadMe at the top
level. The intelligent front end could parse the CVS log on the ReadMe to
present to the user the (latest) release revision(s) available for
download.</FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>I still think a separate repository, let's call it a
staging area might simplify things especially if the update mechanism needed
nothing more than you already have to run PmWiki (php, web server,
browser). Unless there is a php CVS client class out there that can be
reused!</FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>Agreed with a Wiki farm as a good practice -
centralising the management of more than one site.</FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>-Steve.<FONT></DIV></FONT></FONT>
</BODY>
</HTML>