Comments | rebecca2525: Playing around with the OTW archive software on Linux

rebecca2525

Playing around with the OTW archive software on Linux

Jan 07, 2010 18:41

I love fanfiction, I love programming, I love Open Source... so of course I love the Archive of Our Own! I'm not sure if I'm going to sign up as a volunteer, mostly because I always seem to have too little time, but still I'm curious and would like to play around with the software and have a look at the sourcecode on my own. I have been poking ( Read more... )

otwarchive

Comments 5

cesy June 30 2010, 22:23:08 UTC

I think part of the reason we haven't yet documented this bit publicly is because it's still in flux - we're not planning to release the software for people to install on their own servers until version 1.0.

However, you may find the command rake db:otwseed useful - that sets up some sample data, once you've done create:all.

After pulling changes and running migrate, sometimes you'll also need to do rake After.

rebecca2525 July 1 2010, 12:04:31 UTC

Thanks for the info! I can understand that the software is not meant to be installed by users (or admins) at the moment. For me, though, getting familiar with other people's code includes getting my hands dirty and messing around with it and see what happens then, so an own installation is very useful.

At the moment, though, I keep running into a Ruby bug (or a bug in some gem?) which causes the interpreter to crash. :(

cesy July 2 2010, 12:31:19 UTC

What version of Ruby do you have? I know we haven't yet updated everything to work with the latest versions.

If you want to drop in to the chat room at https://fanarchive.campfirenow.com/6a862, that has public access turned on, and someone in there may be able to help in real time.

rebecca2525 July 2 2010, 15:56:53 UTC

My problem has nothing to do with your code and seems to be pretty obscure; I really don't want to waste too much of your time with this.

Stuff worked fine until a routine system update from Ruby version 1.8.7 patch 174 to 1.8.7 patch 249. Now the interpreter dies randomly with a gc_sweep(): unknown data type message when clicking around in my archive. No Ruby code should be able to cause such an error, so it's either a bug in Ruby itself, or in a gem written in C. Google informs me that there are people out there with similar problems, but no-one seems to have a solution. Unfortunately, it's not easy to revert to my previous Ruby version (the only way appears to be to pull the Ruby source from their svn and compile manually), and it might not even work because in the meantime, my gems have been updated, too ( ... )

Thread 5