[katello-devel] Rails 3.2 features

[Eric D Helms]

I have recently spent some time working getting Katello up and running on
the Rails 3.2 stack and thought I would give a status update and point
people to the work in the event they wanted to explore or try it out.

Branch: https://github.com/Katello/katello/tree/rails32

You should be able to install a normal Katello git checkout, switch to the
branch and using RVM get the sever up and running.  Ping me if you run into
issues attempting to try it.

Status:

Green:
Asset Pipeline - fully integrated in both development and production
environments, assets moved to proper locations
Alchemy - submodule entirely removed from project, Alchemy now used as a
gem and Rails engine
Tupane - required defining tupane layouts in the views themselves (much
cleaner way of doing it anyhow)

Yellow:
Spec - Not fully flushed out or tested
Install - see above

Red:
Spec tests - Fixes for a lot of test failures, still a number of failures
exist, largely around the use of "update_attributes"
System Tests - Not run yet
UI Testing - items create and update, however, seeing validation messages
returned upon successful create of an object (multiple requests being made)


Any help trying to tackle or investigate the issues listed above would be
greatly appreciated.  Please reply here or ping me if you try to tackle one
or the other to prevent overlap where possible.  I had previously been
pushing directly into the branch due to the large size and testing nature
of some of the work.  I plan to start pull requesting into the branch from
here on out.


- Eric





On Fri, Dec 7, 2012 at 1:48 PM, Eric D Helms <ericdhelms at gmail.com> wrote:

> My previous experience porting a 3.0 app to a 3.2 application wasn't too
> shabby in the end.  I only had to change application.rb and the rest was
> all asset pipeline related which just involved mostly moving files around
> and creating manifests for the Javacript files.
>
> -Eric
>
>
> On Fri, Dec 7, 2012 at 12:15 PM, David Davis <daviddavis at redhat.com>wrote:
>
>> I thought I'd send a second email in case you guys happened to miss the
>> first one.
>>
>> David
>>
>> ----- Original Message -----
>> > From: "David Davis" <daviddavis at redhat.com>
>> > To: katello-devel at redhat.com
>> > Sent: Friday, December 7, 2012 12:03:20 PM
>> > Subject: [katello-devel] Rails 3.2 features
>> >
>> > I just wanted to make a list of features that we'll get upgrading to
>> > Rails 3.2. I'm sending these out to inform everyone but I think it's
>> > worth reiterating that it's going to be painful to upgrade. It won't
>> > be as bad as going from Rails 2 to Rails 3 but it's not going to be
>> > easy either. Without futher ado...
>> >
>> > * Probably the biggest thing is the asset pipeline. It does
>> > everything from compiling languages (like SASS) to uglifying js
>> > code. Check out more info at
>> > http://guides.rubyonrails.org/asset_pipeline.html
>> > * New migration features. You no longer have to write up/down methods
>> > for the most part. Instead you just write "change" methods. More
>> > info at http://guides.rubyonrails.org/migrations.html
>> > * Multiple levels of has_many :through
>> > * Create key value stores in the database
>> > (
>> http://blog.rawonrails.com/2012/02/using-activerecordstore-with-rails-32.html
>> )
>> > * New active record methods like pluck
>> > (
>> http://api.rubyonrails.org/classes/ActiveRecord/Calculations.html#method-i-pluck
>> )
>> > * Scoped mass assignment. Helpful for locking down attributes per
>> > permission.
>> > (
>> http://launchware.com/articles/whats-new-in-edge-scoped-mass-assignment-in-rails-3-1
>> )
>> > * Slow query logger
>> >
>> http://weblog.rubyonrails.org/2011/12/6/what-s-new-in-edge-rails-explain/
>> .
>> > I've used http://explain.depesz.com/ to help analyze query explain
>> > output from postgres.
>> > * Encrypted fields (passwords, etc)
>> > http://railscasts.com/episodes/270-authentication-in-rails-3-1
>> > * New generator stuff. You can do "rails g scaffold Person name
>> > email" instead of "rails g scaffold Person name:string
>> > email:string". Or if you want to be really crafty: rails g scaffold
>> > Person name:index email:uniq.
>> >
>> > David
>> >
>> > David
>> >
>> > _______________________________________________
>> > katello-devel mailing list
>> > katello-devel at redhat.com
>> > https://www.redhat.com/mailman/listinfo/katello-devel
>> >
>>
>> _______________________________________________
>> katello-devel mailing list
>> katello-devel at redhat.com
>> https://www.redhat.com/mailman/listinfo/katello-devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/katello-devel/attachments/20121221/7754105e/attachment.htm>