information. :)
2012/1/16 jsnark <swr@monmouth.com>
I have about 20 relatively small applications running on the server.
They mostly access the same database tables. Is it more efficient to
combine them into a single application with lots of controllers or to
keep them as separate applications.
ruby 1.9.2
rails 3.0.1
capistrano 2.9.0
passenger 3.0.4
apache 2.2.12
--
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 rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
--They mostly access the same database tables. Is it more efficient to
combine them into a single application with lots of controllers or to
keep them as separate applications.
ruby 1.9.2
rails 3.0.1
capistrano 2.9.0
passenger 3.0.4
apache 2.2.12
--
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 rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
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 rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
