shared hosting is an issue because of the memory needs of Rails and the lack of a proper mod ruby/rails for Apache. Your Mongrels will probably grow and get killed by your shared hosting company, also most of them hate having to setup some totally different systems to host rails. Now, this is when you compare Ruby vs PHP, Java apps have the same issues as Ruby apps.
EngineYard hired people to work on a VirtualMachine called Rubinius as well as a mod for Apache and maybe nginx. When finished, hosting a rails app on a shared host should be way easier. And yes, Tommy is right, in some instances shared DB can be a pain, but that would be a same if you run a PHP app or a Rails app. -Matt On 3/25/08, tommy <[EMAIL PROTECTED]> wrote: > > > Basically, it's easy to deploy sub-optimal Rails applications. I > think the shared hosting problem is mostly database-related. > You really don't have to know much about databases when doing Rails. > This is good and bad thing. Lots of people just ignore the database, > they don't put indices. They do lots of n+1 queries. These acts will > bring a server to its knees a lot of times. > > I was running on a shared hosting and the database was big bottleneck. > > > tommy > > > On Mar 25, 8:25 pm, "Warren Henning" <[EMAIL PROTECTED]> wrote: > > Hi, > > > > The web development I do is for Intranet stuff so the maximum number > > of users I ever get is about 10. I don't even use Rails because the > > databases I have to work with are way too messed up for ActiveRecord. > > So really I don't know what it's like to use a recent version of > > Rails. > > > > I always hear that shared hosting with Rails is difficult. Why is this? > > > > Warren > > > --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
