Shared Controller Logic in Rails Apps

Question

I've worked for several larger clients who have commissioned me to work on multiple rails apps at the same time. Inevitably, this leads to them making one or more feature requests for one app that they expect to be moved to all of the apps, quickly. E.g. A Feedback (email sending) web form. Sharing models betweens apps is pretty straight forward, but sharing controllers and views in a gem/plugin tends to feel a bit wonky.

Are there any best practices that someone could recommend on how to share code like this?

donnior · Accepted Answer · 2012-01-03 17:23:51Z

2

How about packaging your shared code to one gem?

answered Jan 3, 2012 at 17:23

donnior

1,0651 gold badge9 silver badges12 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

trevorgrayson Over a year ago

As I said, that is a possibility, but I don't see that happening a lot in the community. It also makes the code fairly hard to work with as the views/controller/routes would be hidden in a gem. If this is good practice, why wouldn't the community share user registration/sign in or such?

Len Jaffe Over a year ago

They do - The Devise Gem is a user signup and password management solution in a Gem.

Collectives™ on Stack Overflow

Shared Controller Logic in Rails Apps

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related