I've read the techniques mentioned at
https://openacs.org/bboard/q-and-a-fetch-msg.tcl?msg_id=0004TP&topic_id=11&topic=OpenACS. In review of the thread (and linked info):
- technique: Tom Jackson's VAT vhosting module
- notes:
- multiple sites using 1 AOLserver port sharing the same OpenACS (any version),
- limited documentation available
- questions: Allows for different templates with each domain under OpenACS 4.5?
- technique: NSVHR hosting with AOLserver
- notes:
- uses AOLserver as reverse proxy and requires 1 additional AOLserver per domain,
- each OpenACS site is independent,
- also integrates with Tom Jackson's VAT technique,
- apparent future plans include switching the reverse-proxy AOLserver to Apache
- questions: Does patch work for AOLserver 3.4.x? (this technique uses patch with AOLserver3.3ad13)
- technique: Histand's Apache/AOLserver implementation
- notes:
- uses Apache as reverse proxy and requires 1 AOLserver per domain,
- each OpenACS site is independent
- questions: Is this the arrangement used at the test servers openacs.hub.org and openacs1.hub.org?
Has anyone tried using Tom Jackson's VAT hosting module in conjunction with OpenACS 4.5's subsite package, so that for example:
domain1.com resolves to domain1.com (the primary is just another instance of subsite)
domain2.com resolves to domain1.com/subsite2/
domain3.org resolves to domain1.com/subsite3/
For clarification purposes, so that resolving occurs without redirects:
domain2.com appears as serving from domain2.com in browser, search engines etc.
domain3.com appears as serving from domain3.com etc. etc.
