Forum OpenACS Development: Re: Multiple DNS and subsites
An incredible amount of refactoring OpenACS has happened since 5.7, incluiding upgrading tcl syntax. Here is a discussion about compatibility matrix of oacs 5.7 and dependencies: http://openacs.org/forums/message-view?message_id=3920280
And the compatibility matrix: http://openacs.org/xowiki/openacs-compatibility-matrix
Definitely go with naviserver if you can make the change.
Up to january this year, openacs.org had on average 1 error per second.
Concerning the request of Iuri: i did some tests and fixed a few issues (mostly IPv6) and the following testing scenarios work fine:
Testing setup (A):
- http-port: 8009
- https-port: 8443
- base-hostname: localhost
- alternate-hostname: hugo
- main-subsite: /
- alternate-subsite: /hugo
- host-node map: hostname "hugo" -> /hugo/
- apm-parameter (acs-tcl): UseHostnameDomainforReg: 0
In this setup, the subsite (here: /hugo/) has to be given explicit read permission for public, otherwise, one cannot login, since subsite/register won't work (one needs already permissions to reach the subsite main node). Therefore, the site-admin has to grant read permissions to the public explicitly.
Other than this, everything looks ok with setup (A), the subsite works with http and https.
Testing setup (B):
- same as above, but:
- apm-parameter (acs-tcl): UseHostnameDomainforReg: 1
When UseHostnameDomainforReg is activated:
- login is redirected to the main site; the return_url as well.
- login cookies are set on the main-site and are not available on the subsite via the browser (maybe when setting "CookieDomain" and use "domain cookies" and appropriate sub-domain host names; not tested).
- This means that out of the box the user does not stay on the subsite but has to do all authorized work on the main site (which makes management of different users on subsite useless).
Also setup (B) works as well with the newest version in the oacs-5-9 branch. There were some issues in earlier version, but the actual version is fine in this respect. No nginx is involved.
For more details. see: http://openacs.org/bugtracker/openacs/patch?patch_number=848
all the best
@Gustaff, Nice results!
So far, I've set up a fresh installation of OACS 5.9 instance under NaviServer and Postgresql 9.1.
I assigned eventeasy.iurix.com to the same IP that iurix.com uses. Both DNS's point to /var/www/oacs-5-9/. There is only one NS service up, thus a unique config file: iurix.tcl.
I've created eventeasy as an acs-subsite. I've created a host-node eventeasy.iurix.com /eventeasy
However I don't have the behavior expected. the address eventeasy.iurix.com shows the Main Site. It was supposed to display /eventeasy.
Take a look: http://eventeasy.iurix.com/