> > 3. As in 1, there isn't a "Rails Way" to split up huge apps after the > fact. Engines are _mentioned_, but outside of talks I haven't found a > decent writeup. >
Actually a decent writeup on migrating to engines in a production app came out recently, you may find it interesting: http://tech.taskrabbit.com/blog/2014/02/11/rails-4-engines/ Prior to that, the best writeup on engines I had seen was from Pivotal Labs, but it's 2 years old at this point: http://pivotallabs.com/migrating-from-a-single-rails-app-to-a-suite-of-rails-engines/ Adrian -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rails-oceania. For more options, visit https://groups.google.com/groups/opt_out.
