Acts As Subversioned 0.2: For Real…
So, after a very long delay due to graduation, moving, and some other semi life-changing events, acts_as_subversioned 0.2 is now released on RubyForge!
This will probably be the last release of acts_as_subversioned as a standalone plugin. Instead, I’m going to focus my time adding remote connections to the wrapper (for you Subversion types, this will mean RA functionality), as well as creating a Subversion ConnectionAdapter for Ruby on Rails. The goal, in the end, will be to use Subversion as the only backend to a wiki-based program. If all goes well, the two objects (the wrapper and the adapter) will act as a replacement for the MySQL ConnectionAdapter/acts_as_subversioned mashup currently being used.
Thanks to all for your interest so far!
PS: You can get SVN access to project files here. As well, if you are interested in contributing, feel free to sign up as a developer and let me know how you can help!
This stuff is great. I’m just starting to write a little system that uses this.
I’m having a little trouble with the diff method on the SvnRepo class. I’m getting:
uninitialized constant Svn::Info (NameError)
I must need to require something more than just svn/repos and svn/core.
I’m using subversion-1.4.2 and subversion-ruby-1.4.2 on centos.
Thanks again for the great work, hopefully I can help out as needed.
Julian
[From Tim: Hmmm.... I at first thought the subversion bindings were not installed, but, after a quick google, it looks like the subversion-ruby package does the trick. Try requiring "svn/info" and see what happens. I'm not positive of the outcome, but if it fixes things, I'll change it in the next release.]
oops… not sure what version i was using, but just checked out the latest from rubyforge… seems to be working now
Glad to see that you’re up and running
Send me an IM sometime — we should catch up.
Ben
Does acts_as_subversioned offer the same approach to user/authentication as the database plugins? In particular, is ‘application’ user information stored separately from ’subversion’ user information?
[From Tim: Yes, although theoretically, it shouldn't be hard to merge the two, and use only Subversion as your authentication system.]
Nice project. I was reading back through the old posts on the subject looking for some docs (nothing found in the plugin itself), and would like to get some clarification on something.
I get the impression that the acts_as_subversioned is moving in the direction of becoming THE “database” back end for entire Rails projects, rather than just for specific models within that project needing subversions capabilities. Is this true?
[From Tim: That's what I was hoping to do/experiment with -- unfortunately, I haven't found time to get started. The MySQL/Subversion mashup currently there works pretty good, but it seems like a kluge; even if I were to keep MySQL as a "cache" for the most up-to-date Subversion data, it could be written a lot better by encapsulating everything in a custom ConnectionAdapter (this could mean encapsulating the MySQL ConnectionAdapter already there). I'm under the perhaps naive impression that using Subversion as THE backend could do some awesome things for wiki-style applications.]
Oh, and documentation has never been my strong point (it’s not as interesting as the code, but still very needed). If you’d like some documentation, I’d be willing to write something up for you.
I was hoping to use this for document management inside a bigger application that requires a standard database backend for other models. Subversion is great for versioning files. So I’m hoping you keep the MySQL/Subversion mashup at least in some form.