On Sep 16, 2007, at 11:33 AM, bakki wrote:
>
> I have read Ezra's book and the O'Reilly shortcuts and various other
> resources on the Net and most assume you have one app which you deploy
> to shared host, VPS or dedicated host.
>
> Our situation is that we have an ASP app which will be by paid up
> subscription and so the same app will be used by multiple customers
> with their own private db. In addition within the rails tree there is
> a folder for customer uploads and assets.
>
> My client seems to be set on using a dedicated server with shared host
> architecture rather than recommended (Ezra's) VPS slices. I'd like to
> use nginx, mognrel_cluster. The reason why my client is set on shared
> hosting configuration over VPS is that the other contractor on the
> project is convinced that long term maintenance of various open
> source libraries (we need a dozen or more such as wv, enscript,
> antiword, pdf2html etc) on each slice negates the benefit of VPS.
>
> I am looking at nginx cookbook section on the wiki and I see that they
> have for shared hosting:
>
> http {
> server {
> listen 80;
> server_name www.domain1.com;
> access_log logs/domain1.access.log main;
>
> location / {
> index index.html;
> root /var/www/domain1.com/htdocs;
> }
> }
>
> server {
> listen 80;
> server_name www.domain2.com;
> access_log logs/domain2.access.log main;
>
> location / {
> index index.html;
> root /var/www/domain2.com/htdocs;
> }
> }
> }
>
> However when I see the config file for nginx/mongrel I see that the
> directive:
>
> upstream mongrel {
> server 127.0.0.1:8000;
> server 127.0.0.1:8001;
> }
>
> goes in the http section and not the server section. So the question I
> have is, how do I setup mutliple customers on the same box with
> private mySQL databases?
Private databases or database servers? In our shared environment,
we've given the ability to our customers to run their own instance of
PostgreSQL or MySQL on their own ports. (everybody is provided a port
range for mongrels, postgresql, nginx... etc)
>
> This is NOT a very high volume site. There may be 1-2 dozen customers
> on the box each with 1-40 users. I would very much appreciate any
> suggestions, pointers and arguments for/against shared host/VPS
> configurations which I can present to my client. THe main argument
> against VPS seems to be the overhead of creating the VPSs and
> installation/maintenance of libraries. BTW we will be deploying on
> Debian Etch.
Interesting "argument" reasons. We've been doing Rails hosting in a
shared environment for over two and a half years... and we're phasing
it out in favor of our new VPS-solution, Rails Boxcar[1], because
it's been too much of an overhead to make sure everyones applications
were playing nice in the same CPU/memory space. If you restrict the
memory space too much, stuff starts to get quirky... if you open it
up... one persons application bug or hit on DIGG can bring all the
customers sites to a halt. Granted, one could argue that those users
are "getting what they pay for"... but the support calls _still_ come
in and this isn't an appropriate response to them.
Setting up a VPS isn't terribly difficult and when done right...
shouldn't take more work than setting up a new shared user account.
[1] http://railsboxcar.com/
My two cents,
Robby
--
Robby Russell
Founder and Executive Director
PLANET ARGON, LLC
Design, Development, and Hosting with Ruby on Rails
http://www.planetargon.com/
http://www.robbyonrails.com/
+1 503 445 2457
+1 877 55 ARGON [toll free]
+1 815 642 4068 [fax]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Deploying Rails" group.
To post to this group, send email to rubyonrails-deployment@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-deployment?hl=en
-~----------~----~----~----~------~----~------~--~---
