<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Apache and NGINX are the 2 that pop instantly to mind software-wise when doing reverse proxying ... there are other hardware products that I've used like Kemp Technologies LoadMasters that do a fantastic job and can even handle SSL acceleration, but I'm guessing you'd like to do it in software instead of hardware :)<div><br></div><div>From teh googles, it appears that Lighthttpd also does reverse proxying:</div><div><a href="http://www.loadbalancing.org/#Layer-7_Load_Balancing_reverse_proxy_">http://www.loadbalancing.org/#Layer-7_Load_Balancing_reverse_proxy_</a></div><div><br></div><div>-Tom</div><div><br><div><div>On Dec 19, 2011, at 2:23 PM, Matthew Nuzum wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Yes, proxying like this is what I was thinking of. I didn't know if it was easy or hard to do the wild card domains or not. That page you linked to on squid gives an example of precisely this scenario.<div><br></div><div>
Question for anyone: Considering the above would you use Squid or something else? I know Apache and NGINX both do proxying of this type as well. Maybe there's something else out there that may be even better.</div><div>
<br></div><div>What are your recommendations?<br><br><div class="gmail_quote">On Mon, Dec 19, 2011 at 12:19 PM, Tom Pohl <span dir="ltr"><<a href="mailto:tom@tcpconsulting.com">tom@tcpconsulting.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Actually, what Matt has described sounds more like reverse proxy which can be done with several different products, but here's a link for squid:<br>
<br>
<a href="http://wiki.squid-cache.org/ConfigExamples/Reverse/MultipleWebservers" target="_blank">http://wiki.squid-cache.org/ConfigExamples/Reverse/MultipleWebservers</a><br>
<span class="HOEnZb"><font color="#888888"><br>
-Tom<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Dec 19, 2011, at 11:51 AM, Eric Junker wrote:<br>
<br>
> I don't know if this will solve your problem, but Apache "Dynamically configured mass virtual hosting" may be useful to you<br>
><br>
> <a href="http://httpd.apache.org/docs/2.2/vhosts/mass.html" target="_blank">http://httpd.apache.org/docs/2.2/vhosts/mass.html</a><br>
><br>
> Eric<br>
><br>
> On 12/19/2011 10:05 AM, Matthew Nuzum wrote:<br>
>> Hello, I'd like to set up an environment at home where I can host<br>
>> multiple VMs (or maybe even an open stack setup) in order to expose web<br>
>> services to the public.<br>
>><br>
>> I have one server that runs constantly, it could act as a proxy or<br>
>> forwarder. I have two more servers that will run virtual machines<br>
>> (virtualbox or openstack probably).<br>
>><br>
>> The goal is to make staging and development easier. Therefore there are<br>
>> two varieties of sites I will run:<br>
>><br>
>> * "Production" type sites where a virtual machine runs a web server on<br>
>> port 80<br>
>> * "Development" type sites where a Django or Rails site is running on<br>
>> port 8080 or 8000<br>
>><br>
>> My intention is to point a wild-card domain to my home router<br>
>> (*.<a href="http://v5.iowatechies.com/" target="_blank">v5.iowatechies.com</a> <<a href="http://v5.iowatechies.com/" target="_blank">http://v5.iowatechies.com</a>>) and what I'd love is<br>
>> to be able to map *.<a href="http://x.v5.iowatechies.com/" target="_blank">x.v5.iowatechies.com</a> <<a href="http://x.v5.iowatechies.com/" target="_blank">http://x.v5.iowatechies.com</a>>.<br>
>> So for example, EC2 uses something like this for x: ec2-11-22-33-44<br>
>> (wich is a pointer to 11.22.33.44 IP address). I'd be happy with this<br>
>> but I'd love to be able to have multiple domains at each host, hence the<br>
>> wildcard *.<a href="http://x.v5.iowatechies.com/" target="_blank">x.v5.iowatechies.com</a> <<a href="http://x.v5.iowatechies.com/" target="_blank">http://x.v5.iowatechies.com</a>>.<br>
>><br>
>> What would you recommend? And, for the record, imho, simpler is better<br>
>> than better.<br>
><br>
> _______________________________________________<br>
> Cialug mailing list<br>
> <a href="mailto:Cialug@cialug.org">Cialug@cialug.org</a><br>
> <a href="http://cialug.org/mailman/listinfo/cialug" target="_blank">http://cialug.org/mailman/listinfo/cialug</a><br>
<br>
_______________________________________________<br>
Cialug mailing list<br>
<a href="mailto:Cialug@cialug.org">Cialug@cialug.org</a><br>
<a href="http://cialug.org/mailman/listinfo/cialug" target="_blank">http://cialug.org/mailman/listinfo/cialug</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthew Nuzum<br>newz2000 on freenode, skype, linkedin and twitter<br><br><div>
<br class="webkit-block-placeholder"></div><p><span>♫</span> You're never fully dressed without a smile! <span>♫</span></p><div><br class="webkit-block-placeholder"></div><br>
</div>
_______________________________________________<br>Cialug mailing list<br><a href="mailto:Cialug@cialug.org">Cialug@cialug.org</a><br>http://cialug.org/mailman/listinfo/cialug<br></blockquote></div><br></div></body></html>