Re: version control/change history plugin?

On Thu, 3 Aug 2006, will guaraldi wrote:

> I think the easiest thing to do is to keep your blog in a CVS/SVN repository. 
> Every time you make a change to a blog entry, you check the change in. 
> CVS/SVN maintains versions and history of your entries outside of PyBlosxom.
>
> Then write a plugin that pulls the history for a specific entry from CVS/SVN
> when given teh querystring ?version=history or something like that. And then
> for specific diffs between entry versions ?version=diff&from=12&to=13 or
> something like that.

good call. i like this, since it lets pyblosxom and cvs/svn each do what they
do best. even better, a few people have discussed it, and an svn pyblosxom
plugin (minus history and diffs) already exists:

http://www.baus.net/svnpyblosxom

(discussion at http://mg.pov.lt/blog/pyblosxom-setup.html and
http://cubiclemuses.com/cm/blog/less_blog.html .)

the main problem is resources and latency. you have to spawn an svn process
for every request, since svn is the source of the original post creation date.
that's both expensive and very slow.

christopher baus' plugin solves this by using a dedicated cache process,
memcached. it sounds like it works, but it's really heavyweight, and not an
option for pyblosxom installations on shared hosting plans (ie most of them).

i haven't looked at the other date-preserving plugins, but one of them might
work instead. then you'd only need to run the svn client on diff and history
requests. still far from ideal, though.

thoughts?

-Ryan

--
http://snarfed.org/

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV