Using CVS to archive CMS Content
Posted: Tue Sep 14, 2004 9:06 am
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.
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.