Andrew Neil wrote:
On 5 Oct 2008, at 00:30, Jay Levitt wrote:
Just a thought I had in the shower:
Most attempts at CMS version control end up reinventing large parts of
subversion/git/etc. inside the database. Instead...
Why not use something like FuseFS to implement a filesystem that maps
the Radiant asset tree to paths like "/dev/radiant/pages/home_page"?
Then use the version control system of your choice.
That's not wacky, it's a great idea!
The file_system extension was designed for this purpose. Check it out here:
http://github.com/nelstrom/radiant-file-system-extension/tree/master
Ah hah! I saw that yesterday, but (so far, at least) it looks like it's
targeted at explicit save/loads. Are you thinking of taking it in the live
filesystem direction? That would be very cool.
I did a little more Googling on FuseFS, and it seems that the RubyForge
project is stagnant, but that a few people have got some version of it
working on some OS's sometimes...
http://www.datanoise.com/articles/2007/3/9/macfuse-and-ruby-fusefs-extension
I don't have an immediate need for version-control myself (other than It
Would Be Cool), but, well, it WOULD be cool.
Jay
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
