-> > -> Ok I got aolserver working so what do I need to do to setup two websites to
-> > -> point to one IP I could easily do it with apache but this server is whole
-> > -> new ball game. ;)
-> >
-> > I've found it very easy to do this with Apache acting as a front-end
-> > proxy server to one or more AOLserver instances.  I have yet to find simple
-> > instructions for doing this with AOLserver natively -- perhaps I'm missing
-> > something, though...
->
-> I assume you have each of your nsd's using nssock, and Apache doing the
-> front-end proxy to each of these individual nsd's.

Yep.

-> All you'd need is one more nsd with nsvhr and nssock to replace Apache.
->
-> If you're interested in trying it, I'd be happy to walk you through
-> configuring the proxy nsd -- we could keep record of the walk-through
-> as the basis for a HOWTO for setting up nsvhr/nssock to implement
-> software virtual hosts.

I'll try this on my own over the weekend, and send you questions when I
run into problems.  I should be able to write it up pretty quickly.

-> Then, you could switch all your nsd instances to nsunix (still running
-> nsvhr/nssock in the proxy, of course) to boost performance -- AND, give
-> each of your virtual nsd's access to the client IPs of the incoming
-> requests, which is important if you want to do web log analysis ...

Most of my virtual hosts run on my development machine, on which Apache
is a necessity (for other developers/programs); this is why I haven't
really played with nsvhr before.

Incidentally, if anyone wants to try the Apache way, if only for
comparison, it's the second link under this:

        http://www.idyll.org/~t/www-tools/

FWIW, I think Apache config files are uglier than anything except for
printcap config files, so I'd love to have an AOLserver-specific config
if only to show the difference!

--titus

Reply via email to