For each domain, just define a virtual host in apache. Each virtual host definition can have its own webserver docs directory.
For https, you need one IP address dedicated to each HTTPS virtual host domain. All this is common apache stuff. Just refer to the apache docs online, which are usually good at explaining stuff. On Sep 12, 2010, at 7:05 PM, Ken Anderson wrote: > All, > > As an apache neophyte, I would appreciate some thoughts on how to best set > this up. > > On the same machine, I'll be running a public HTML marketing site (no WO), a > public HTTP WO site (all direct actions), and a private HTTPS WO site > (components, for management). > > What's the correct way to configure Apache for this? > > Thanks for any thoughts! > > Ken _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/kieran_lists%40mac.com > > This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
