From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: OT: iptables w/ 2 web servers
Date: Thu, 24 Sep 2009 18:58:06 +0100 [thread overview]
Message-ID: <DB3C4024-E419-4BAC-8A3F-A5364008259C@stellar.eclipse.co.uk> (raw)
In-Reply-To: <loom.20090924T171825-62@post.gmane.org>
On 24 Sep 2009, at 16:30, James wrote:
> ...
> So the best I can do is forward all traffic( 80, 443, etc) for the
> group of websites to a proxy behind the firewall, then use software
> such as what kashani suggested (proxypass, Squid, ngnix,
> lighttpd, or Varnish) and parse the traffic with some form of
> vhosts implementation on a single server (nated IP)?
I think you can simply forward to server A. If the site is on server A
then it's served, if it's on server B then in the vhosts for that site
on server A you can proxy for server B. Of course if server A goes
down then you're stuffed.
> Then if the load of the combined virtual hostings becomes too large,
> I use a group (cluster) of servers that and implement some sort of
> load
> balancing across the machines that each contain complete copies of
> each website?
>
> Then there is the question of how to keep the individual machines
> 'in sync' and the limitation that once a machine is saturated
> (performance
> suffers too much due to insufficient resources) there
> is no solution for expansion?
This surely exceeds what you'll be hosting on a NATted home connection?
> One last thing. I can get a small subnet of say 5 IP address from my
> ISP for an additional 20/month. That that help me? I want to put up
> dozens of small charitable web sites. None will have a huge user base,
> but I was going to stream some limited video from each of them.
Yes, this certainly overcomes the original problem. You have a
separate IP for each server and the DNS for each site directs
appropriately.
Not all routers support this configuration and, 5 years ago, I found
it a little cumbersome to set it up in Linux (it's called "bridging").
No doubt the situation has improved a lot since then.
Stroller.
next prev parent reply other threads:[~2009-09-24 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 21:35 [gentoo-user] OT: iptables w/ 2 web servers James
2009-09-23 21:49 ` kashani
2009-09-24 3:48 ` Stroller
2009-09-24 15:30 ` [gentoo-user] " James
2009-09-24 16:58 ` kashani
2009-09-24 17:58 ` Stroller [this message]
2009-09-25 12:40 ` Etaoin Shrdlu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DB3C4024-E419-4BAC-8A3F-A5364008259C@stellar.eclipse.co.uk \
--to=stroller@stellar.eclipse.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox