Re: [Zope] SiteAccess (Enh. VHM) still needed, or merged to Zope?
Am Mittwoch, den 28.09.2005, 20:49 -0400 schrieb Jeff Kowalczyk: Most references I find (google, The Plone Book - McKay, Building Websites W/ Plone - Cooper) on virtual hosting Zope behind Apache recommend starting with sfm's SiteAccess enhanced Virtual Host Monster product: http://www.zope.org/Members/sfm/SiteAccessEnhanced/view Reportedly last updated 2001-08-19, is SAE really so mature that it has not subsequently needed updates or merited a merge into Zope's own VHM? I need to map the incoming URL http://(*.)foo.com/new/* to a Plone instance at http://localhost:8080/foo/*; , and later change the inbound mapping to http://(*.)foo.com/* after customer acceptance. I'm guessing that this is the most vanilla virtual hosting requirement possible, and I want to use the simplest configuration to accomplish it. If the old SEH 2.1.0 is the recommended tool with Zope-2.8.1, I'm sure the existing docs will be enough to figure it out. Thanks. I believe Zopes VHM is the very SEH but updated since it became part of zope. In recent zope versions there is in fact nothing to do to use it because an instance is automatically created. You only do the usual apache rewrite dance and be ready :) ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] SiteAccess (Enh. VHM) still needed, or merged to Zope?
Jeff Kowalczyk wrote: Reportedly last updated 2001-08-19, is SAE really so mature that it has not subsequently needed updates or merited a merge into Zope's own VHM? Use the one that ships with Zope, it's likely to be better maintained... I need to map the incoming URL http://(*.)foo.com/new/* to a Plone instance at http://localhost:8080/foo/*; , and later change the inbound mapping to http://(*.)foo.com/* after customer acceptance. Are you front ending with Apache? If not, you should be... I'm guessing that this is the most vanilla virtual hosting requirement possible, and I want to use the simplest configuration to accomplish it. If the old SEH 2.1.0 is the recommended tool with Zope-2.8.1, I'm sure the existing docs will be enough to figure it out. Thanks. There are plenty of examples of how to do this using the normal stuff that ships with Zope... cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] SiteAccess (Enh. VHM) still needed, or merged to Zope?
Most references I find (google, The Plone Book - McKay, Building Websites W/ Plone - Cooper) on virtual hosting Zope behind Apache recommend starting with sfm's SiteAccess enhanced Virtual Host Monster product: http://www.zope.org/Members/sfm/SiteAccessEnhanced/view Reportedly last updated 2001-08-19, is SAE really so mature that it has not subsequently needed updates or merited a merge into Zope's own VHM? I need to map the incoming URL http://(*.)foo.com/new/* to a Plone instance at http://localhost:8080/foo/*; , and later change the inbound mapping to http://(*.)foo.com/* after customer acceptance. I'm guessing that this is the most vanilla virtual hosting requirement possible, and I want to use the simplest configuration to accomplish it. If the old SEH 2.1.0 is the recommended tool with Zope-2.8.1, I'm sure the existing docs will be enough to figure it out. Thanks. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
