inicio mail me! sindicaci;ón

Yet another RailsCollab demo

Recently i have had another go at tweaking RailsCollab, the pet project of mine (which i have mentioned previously).

After moving the source repository from Subversion to Git, i decided to add in a long standing missing feature – the web-based configuration editor.

Configuration Editor

Originally i pretty much stayed away from implementing this as Ruby on Rails was a real pain in the ass when it came to deployment, so i couldn’t implement a configuration loader that i knew would work in 90% of deployment cases.

That was, until recently when Phusion Passenger was released.

Phusion Logo

For those of you that don’t know, Passenger is an Apache module which allows you to simply drop in your Rails application and run it with practically zero configuration. It pretty much falls under the “it just works” category. I have no doubt that anyone using RailsCollab will prefer using Passenger to deploy. Consequently, i have been able to implement a rather nice configuration loader based on this assumption.

Which brings me to the demo. A short while back, my web host, DreamHost added Phusion Passenger support to their web servers. Factor everything together, and you have… the RailsCollab demo!

Link to the demo

“But wait!” you ask, “how do i login?”. Well, using OpenID of course. As with my previous demo, you should be able to select the “Use OpenID” checkbox and type in your OpenID to login.

OpenID Logo

This will automagically register you with the system, adding you to the “OpenID” company and the “RailsCollab” project. Afterwards if you want, you can reset your password so you can login using a regular username & password, though personally i think typing in your OpenID is a better idea.

Note that your OpenID provider needs to support handing over identity fields in order for RailsCollab to correctly register you. MyOpenID is an example of a provider that supports this. Also note that if there is a user with a duplicate username or email in the system, registration will fail.

One more thing

The RailsCollab demo also supports the Basecamp API. This means that you can take any existing widget, program, or service that integrates with Basecamp and use it with RailsCollab. e.g. Avalanche, Freshbooks, or Cashboard

So what are you waiting for? Try the demo already!: :)

http://id.reactioncontrol.com/mpolito said,

June 6, 2008 @ 5:03 pm

I’ve been watching this project for a while but have never contributed. What can I do to help?

James Urquhart said,

June 7, 2008 @ 12:42 pm

mpolito,

To help? Well, at the moment i’ve not really got any roadmap defined, so that is really an open ended question.

Things i can think of off the top of my head:

  • Use it and find all of the bugs
  • Implement the configuration option for changing the current theme (so one can easily use all of those lovely ProjectPier themes)
  • Make a simple plugin system (To keep up with ProjectPier, perhaps something like in Retrospectiva)
  • Write some unit tests (as of yet, i haven’t really bothered with this)

Thanks for your interest.

~ James

Larry Cummings said,

June 9, 2008 @ 6:53 pm

Playing around with RailsCollab over the weekend. Pretty nice!

I noticed that Administration -> System pulls up a Localization error, which I can’t figure out. And the Basecamp Migration script took quite a long to time to get through (probably mostly from my lengthy Basecamp export file).

James Urquhart said,

June 9, 2008 @ 7:23 pm

Larry,

Thanks for trying out RailsCollab.

The configuration options for Administration -> System have not been localized, thus the localization errors. In ActiveCollab they are usually hidden, thus why i haven’t localized them yet.

Nice to hear you got the Basecamp Migration working. Since i only had one free Basecamp account, i didn’t have much to test the feature with. So it’s no surprise that it is a little bit slow.

Larry Cummings said,

June 10, 2008 @ 5:07 am

Ah, well that makes sense on the Admin screen.

The Basecamp import isn’t slow from an execution perspective. It was a great deal of trial, error, edit, repeat to get my import to complete successfully. I ended up getting rid of all my time records (which wasn’t that big a deal) and tweaking some of the assignments of task items.

I could send you the diff of my final Basecamp import file if you want. I did make a couple of very, very minor changes to the importing script, which I can also send you if you like.

James Urquhart said,

June 11, 2008 @ 8:32 pm

Larry,

I would be very interested in the changes made to the import script, especially if they improve the accuracy of the import.

Thanks again.

~ James

Matt Gilkeson said,

August 18, 2008 @ 5:56 am

I get an error when trying to log in… “Erroneous identity fields provided.” Please help…

James Urquhart said,

August 18, 2008 @ 4:37 pm

Matt,

Your OpenID provider needs to provide a nickname, email, and full name. If for whatever reason it doesn’t, then you will get that error.
(Come to think of it i’d better go over that code again just to check it works correctly)

To save you the trouble of figuring that all out, i have made you an account with your OpenID.

Have fun.

~ James

RSS feed for comments on this post · TrackBack URI

Leave a Comment

Close
Powered by ShareThis