Sunday, September 7, 2014
A rails engine is how I'd do it myself but if that's off the table, the only way I see that could remotely (and poorly) work would be to manage the work in git branches somehow.
-- you'd have to be very careful and it's a bad idea - but could be possible.
have a core branch of code and a set of production branches... when the core changes you can merge it over the production branches. just don't ever merge the production branches over the core... lol
it's a bad idea... use an engine - they work nicely and aren't very hard to do
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/2efa035c-ac82-4a6e-afbd-fa184eb599e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment