Page 1 of 1

Using CVS to archive CMS Content

Posted: Tue Sep 14, 2004 9:06 am
by CoderGoblin
viewtopic.php?t=15190 mentions building a "CVS" System although the question was more based on how to store the information zip etc.

1) Has anyone built or considered using PHP based CVS interface to actually archive information from their CMS to check things in and out of an archive.

As this is only an archive system editing the CVS process would be
-Check Out Existing Archive if exists
-Overwrite with Current Content
-Commit.

Advantages:
-Automatic version control.
-Easy(ish) difference function.
-Able to rollback
- Smaller file size for large content blogs.

Disadvantages
- Complexity
- Small Content Blogs with infrequent changes take up additional space.
- System calls required therefore windows OR linux based.

Can anyone else think of any advantages/disadvantages?

2) Does anyone know of any PHP "classes" for CVS. I have looked on the web with no luck.

Re: Using CVS to archive CMS Content

Posted: Tue Sep 14, 2004 7:04 pm
by Weirdan
CoderGoblin wrote: 2) Does anyone know of any PHP "classes" for CVS. I have looked on the web with no luck.
http://cvs.php.net/pecl/cvsclient/ ?

Posted: Wed Sep 15, 2004 6:13 am
by Buddha443556
Can anyone else think of any advantages/disadvantages?
Would need to run a CVS server, most shared hosts won't allow that.
CVS isn't exactly binary file friendly.

200th Post!

Posted: Wed Sep 15, 2004 6:23 am
by CoderGoblin
Thanks for the responses.

Buddha443556 - That's ok . Design is for our own server.
Weirdan - I was really looking for a PHP web based CVS program and having access to the PHP classes if any therein. Searched the web using "CVS client PHP" and found some but will look at them later as I have been diverted onto something else.

But keep your ideas/comments coming. There are appreciated.

Posted: Wed Sep 15, 2004 12:45 pm
by McGruff
A troll through some open source wiki code might also turn up something useful.