You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Jeff Stuart <js...@computer-city.net> on 2002/10/10 16:15:06 UTC

Content Management/Deployment with SVN.

On Thu, 2002-10-10 at 04:56, Morten Ludvigsen wrote:
> I see we are thinking along the same lines :-)
> 
> My thought is to have information on which files should be accessible in 
> an XML file "files.xml" (under SVN of course):
> 
>   <?xml version="1.0"?>
>   <files xmlns="http://twops.dk/files/1.0">
>     <dir name="/">
>       <file name="slam.html">
>         <active from="20020801T0000" to="20020831" tag="/version/23" />
>         <active from="20020901T0000" to="infinity" tag="/version/25" />
>       </file>
>       <dir name="images">
>         <file name="bam.gif">
>           <active from="20020801T0000" to="20020831" tag="/version/23" />
>           <active from="20020901T0000" to="infinity" tag="/version/25" />
>         </file>
>       </dir>
>     </dir>
>   </files>
> 
> When a change is commited to this file it is immediately svn-updated on 
> any servers that need it (or it could be accessed through HTTP).
> I would probably have a branch for test and production:
> 
>   [Repository]/releases/trunk/files.xml
>   [Repository]/releases/test/files.xml
>   [Repository]/releases/prod/files.xml
> 
> One would only edit files.xml in the trunk, and copy it to test or prod when needed.
> So the production site would use files.xml from [Repository]/files/prod/files.xml.
> The version numbers in files.xml are not revision numbers (i know that now :-).
> So when the server needs slam.html the tag is looked up in files.xml. If it
> already has that version of slam.html in cache it can use that, knowing that
> it has not changed. This is especially important if further processing is needed
> (ex. an XSLT transformation) before it is served to the user.
> 
> Any thoughts?

VERY interesting... I hadn't thought of something like that.  (I've not
used XML yet very much. :))  You might even be able to use it to
automatically create a tarball/release package to be deployed across
multiple servers if you're using a farm.   HMMM.... 

> > The more I play with SVN, the more AMAZED I am at it's potential! 
> > Whoever decided to use WebDAV and Apache is a GENIUS! :)
> 
> I agree - also SVN is portable, handles binary files (ever tried that with CVS?) and is free :-)
> 

GAH!  PLEASE do NOT remind me! LMAO  (In other words, yes I DID try that
with CVS.  It umm was NOT fun! LOL)

I just LOVE how SVN handles it.  IE the images checked in with NO
problems at all. :)

> Regards,
> 
> Morten Ludvigsen
> 2-People Software
> Denmark
-- 
Jeff Stuart <js...@computer-city.net>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org