Ruby 1.9.3/Rails 3.2.x

[hading2]

Hi,

I've resumed working on a version of Bibapp for Ruby 1.9.3 and Rails 3.2.x. since there have been some questions about that. It will be available from the GitHub site for anyone who is interested in perusing it or trying it out (as the rails-3.2 branch). 

I'll give a warning here when I think it is ready and some time after that (I don't know how long - a week or two perhaps?) I'll fold it into master. When that happens if one wants to continue running master it'll be necessary to change the ruby being used to 1.9.3, and I'll tag the final (unless someone else wants to continue working on it) version of the 1.8.7 code.

While I'm working on it some features may be absent.

• The Tolk gem for doing translations inside the application is temporarily gone. We used a customized version and it's not compatible with Rails 3.2. I need to review the changes we made and apply them to a more current version, but since as far as I know no one is currently working on a translation I don't consider this urgent.
• I've disabled some of the stuff around using OpenID or OAuth. I don't know if anyone else is using those anyway. I'd be happy to take that out since it was basically a proof of concept (though we do use the Omniauth framework to do Shibboleth authentication at UIUC, so it wouldn't disappear entirely, just the specific stuff I did as a proof of concept). I don't know if anyone is using it though.

There may be other things that come out for a while as I do this, although I suspect that most of the other stuff is okay.

Howard

[Jason Stirnaman]

We're using oauth for CAS authentication, but I'm fine with removing the proof-of-concept implementation.

I'll give the branch a try as soon as I can. Thanks!

Jason

--
You received this message because you are subscribed to the Google Groups "bibapp" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bibapp+un...@googlegroups.com.
To post to this group, send email to bib...@googlegroups.com.
Visit this group at http://groups.google.com/group/bibapp?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Howard Ding]

On 3/14/2013 5:44 PM, Jason Stirnaman wrote:
> We're using oauth for CAS authentication, but I'm fine with removing
> the proof-of-concept implementation.
> I'll give the branch a try as soon as I can. Thanks!
>
>

Thanks. Given the state of the things I'll just be doing a lot of
clicking through the app and fixing things that are broken.

I'm not sure exactly how you're doing your auth stuff, so it's
conceivable that I'll break it. Omniauth underwent some significant
changes from 0.3 to 1.0 and I'm not sure how that's going to play out. I
used the newer version for a different project, but I haven't actually
tried to upgrade one yet.

Howard

[hading2]

I've spent some time working on getting Tolk up to speed with Bibapp for Rails 3.2 and to be honest I'm not sure it's going to be worth the effort, at least in the short term. I'm going to punt on it for now. There are just a lot of loose ends that seem to need to be tied up before it can integrate, even though Bibapp seems to function fine without tying them up.

[hading2]

Hi,

I think that Bibapp for ruby 1.9.3/rails3.2 is good to go now. There are some things that can (and will) still be done, but it functions and I have it deployed here at UIUC. Barring any serious objections on 1 Apr I'll plan to tag the ree/rails3.0 version as a release, merge the current rails-3.2 branch into master, and then tag that as a first release for the next major version. At that point if you want to use the new release or stay with the master you'll have to change your set up to use ruby 1.9.3. (I found that the hardest part of this for us was getting our capistrano deploy to make the changeover gracefully.) If you want to continue with ree (ruby 1.8.7) you'll have to stay with the old code. I'll update the wiki as best I can at that point as well.

Some specifics:

- Omniauth appears to be working fine (it works with our Shibboleth), however if you are using it you may need to add your particular strategy in. Since this is a move from Omniauth 0.3 to 1.0 there may be some differences - you'll have to check if you're using it. I've removed the stuff related to OpenID and OAuth that I had in there as a proof of concept (or at least commented it out), but people should be able to use a variety of auth methods via Omniauth without much difficulty. (Jason - you're the only one who has said that you do, so if there is anything I can do to help here let me know.)

- I haven't put Tolk back in (for facilitating translations). I hope to do so, but there is some more work to do before I think I even have a chance.

- Many gems are updated for this version

- Rails 3.2 offers some things like the asset pipeline that I haven't taken advantage of yet, but those sorts of things are on the radar, as is some additional updating of gems that I skipped for now because it would have required a bit of code change that I didn't have time to do.

Howard