Plugins.
On Feb 15, 8:25 pm, ericindc <[email protected]> wrote:
> I come from a PHP environment where we have a "library" of sorts that
> contains various functionality in the form of object-oriented
> classes. The classes can be tied into any new project and the
> functionality of that class is gained without any duplication of
> coding efforts.
>
> In learning Ruby on Rails, I'd like to create something similar for
> use in developing Rails applications. Is there a best practice for
> said "library" of functionality? How best is this code base shared
> between applications? Most importantly, how can updates to said
> library be easily reflected across all applications?
>
> For instance, we want to have a single login/logout user capability
> between applications, since all of our applications will share the
> same userbase. I know restful_authentication exists, but I'm working
> on rolling my own as a learning exercise.
>
> Give a User Model, Session (login/logout) and User (registration/
> activation) Controllers, and an Authentication Module, what is the
> best way to share this code set across applications?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
