Virtual Hosting configuration for Zope
I've put together the following solutions for virtual hosting of domains and I'm looking for some feedback from the list. The solution uses TinyTable, Virtual Host Monster and AccessRule and a DTML method to process all inbound requests by domain name similar to the way in which SiteRoot script things. The best part is that once set, the AccessRule does not need to be modified to add new hosts. Host to folder mapping is performed via entries in the TinyTable, the rest of the configuration is static. I would think it would be simple to implement something like this as a product, though it is beyond my current skill set. I'd like to enhance it a bit further so that it can handle hostnames in addition to just domain names. I'd also be happy to hear any feedback on this. Tested with Zope 2.3.0 and TinyTable 0-8-2. Virtual Host Monster and AccessRule support are built into 2.3.0 Here it is: Create a folder in Root called VHosts Inside VHosts create a folder for each Virtual host Inside each new Virtual host's folder , create a Virtual Host Monster called VHM Inside VHosts, create a TinyTable called HostsTable Give the Tiny Table the following columns : domain, folder Create records for domain to folder mapping as shown here: "domain1.com", "Folder1" "domain2.com", "Folder2" Where the domain names are the virtual names for your server and the folder names are the folders created inside VHosts. Entries are CASE SENSITIVE and MUST match the folder names created in the earlier step. Enter all domains in lower case. Inside VHosts create the following DTML Method: Name: gethostfolder <dtml-in "VHosts.HostsTable(domainname)"> <dtml-return folder> <dtml-else> <dtml-return "'NULL'"> </dtml-in> In the Root, create a DTML called AccessRule AccessRule in Root Folder =================== <dtml-let hostname="_.string.split(_.string.lower(_.string.split(HTTP_HOST, ':')[0]),'.')[-2:]" domainname="hostname[0] + '.' + hostname[1]" vhmcode="VHosts.gethostfolder(_.None, _, host=domainname)"> <dtml-if "vhmcode<>'NULL'"> <dtml-if "_.string.split(_.string.lower(PATH_INFO), '/')[-1:]==['manage'] or _.string.split(_.string.lower(PATH_INFO), '/')[-1:]==['manage_main'] or _.string.split(_.string.lower(PATH_INFO), '/')[-1:]==['manage_workspace'] "> <dtml-if "TraversalRequestNameStack[-2:]<>[vhmcode,'VHosts']"> <dtml-call "REQUEST['TraversalRequestNameStack'].extend([vhmcode, 'VHosts'])"> </dtml-if> <dtml-else> <dtml-call "REQUEST['TraversalRequestNameStack'].extend(['VHM', vhmcode, 'VHosts'])"> </dtml-if> </dtml-if> </dtml-let> It should look like this: Root- AccessRule VHosts- HostsTable gethostfolder Folder1- VHM index_html Folder2- VHM index_html Security Settings: gethostfolder method: no anonymous access, proxy as manager, manager has full rights. HostsTable: No anonymous access, manager full rights AccessRule: Proxy as manager Now, to enable the system, Use the Root folder's Add->SetAccessRule option and enter "AccessRule" (without quotes) and click Set. Requests for domain1 will be drawn from Folder1, 2 from 2 etc.. Managent of the virtual domain will show only the VHosts folder contents for the selected site. Management of the root site will show the root. Access to unsupported domains will fall back to root. (perhaps to be a redirect to a 404 page in the future) Display the mappings with /VHosts/HostsTable or via the management interface. Use http://hostname/_SUPPRESS_ACCESSRULE/manage to deactivate the AccessRule if you have any problems accessing the system. All feedback welcome. To the list please. Alan Capesius, MCSE Tech World, Inc. http://twsite.bizland.com/zopetips.htm
I've put together the following solutions for virtual hosting of domains and I'm looking for some feedback from the list.
The solution uses TinyTable, Virtual Host Monster and AccessRule and a DTML method to process all inbound requests by domain name similar to the way in which SiteRoot script things. The best part is that once set, the AccessRule does not need to be modified to add new hosts. Host to folder mapping is performed via entries in the TinyTable, the rest of the configuration is static. I would think it would be simple to implement something like this as a product, though it is beyond my current skill set.
I might be missing something here, but isn't it easier to use just Virtual Host Monster in Zope (add once), configure Apache with ProxyPass and the stuff needed for mass virtual hosting and be done with it? Or am I missing something? Cya Jonathan
On 21 Mar 2001 11:16:49 +0100, Jonathan (Listserv Account) wrote:
I've put together the following solutions for virtual hosting of domains and I'm looking for some feedback from the list.
The solution uses TinyTable, Virtual Host Monster and AccessRule and a DTML method to process all inbound requests by domain name similar to the way in which SiteRoot script things. The best part is that once set, the AccessRule does not need to be modified to add new hosts. Host to folder mapping is performed via entries in the TinyTable, the rest of the configuration is static. I would think it would be simple to implement something like this as a product, though it is beyond my current skill set.
I might be missing something here, but isn't it easier to use just Virtual Host Monster in Zope (add once), configure Apache with ProxyPass and the stuff needed for mass virtual hosting and be done with it?
Or am I missing something?
Other than the big one, namely installing and setting up Apache? ;^)= Bill
Or am I missing something?
Other than the big one, namely installing and setting up Apache? ;^)=
Well duh ;) And here I am 24 hours later trying to accomplish the same thing, Zope behind Squid, without Apache :) Cya Jonathan
Alan, I do something similar, but I do it with an access rule only (and adding a simple Site Root to each folder that has all properties blank) Basically, I have an access rule that looks at the hostname (complete hostname, not just domain name) and then redirects to a properly named folder off the root. Here is the access rule if you want to take a gander: <dtml-let virtual_dir="_.string.lower(_.string.join(_.string.split(_.string.split(HTTP_HOST, ':')[0],'.')[:],'_'))"> <dtml-if "virtual_dir != 'manager_host_com'"> <dtml-if expr="virtual_dir"> <dtml-call "REQUEST.set('SiteRootPATH', '/')"> <dtml-call "REQUEST['TraversalRequestNameStack'].append(virtual_dir)"> <dtml-else> <dtml-call "REQUEST.set('SiteRootPATH', '/')"> </dtml-if> </dtml-if> </dtml-let> Basically, what this does is: 1. Grab the hostname, convert to lowercase (for those that are CAPS challenged) and then replace . with _ 2. Look and see if the hostname is the name of our management alias hostname (the hostname designated to be the Zope root, manager.host.com in this case) and if it is, simply do nothing and just continue on normally 3. If it's not our management hostname, then look and see if we have a folder that matches (IE: host_domain_com) 4. If we have a folder that matches, set our SiteRoot stuff, and add the path to the name stack Simple solution really, and was done before the creation of VHM's in Site Access. I have several servers running with this solution and it works quite well.. The one drawback to this method is the case of wanting more than one site pointed to the same folder. Haven't figured out a complete solution for that yet ;-) --Adam On 21 Mar 2001 23:01:26 -0600, Alan Capesius wrote:
I've put together the following solutions for virtual hosting of domains and I'm looking for some feedback from the list.
The solution uses TinyTable, Virtual Host Monster and AccessRule and a DTML method to process all inbound requests by domain name similar to the way in which SiteRoot script things. The best part is that once set, the AccessRule does not need to be modified to add new hosts. Host to folder mapping is performed via entries in the TinyTable, the rest of the configuration is static. I would think it would be simple to implement something like this as a product, though it is beyond my current skill set.
I suppose you could do multiples with a simple -or- arrangement. Your solution (and mine to some extent) are similar to the SiteRoot examples. My goal was to take the editing of the accessrule out of the picture so I (or others) don't accidentally lock everyone out. The HostsTable accomplishes this nicely. It also allows easy multiple aliasing. thanks.
-----Original Message----- From: M. Adam Kendall [mailto:mak@kha0s.org] Sent: Thursday, March 22, 2001 10:06 PM To: Alan Capesius Cc: zope@zope.org Subject: Re: [Zope] Virtual Hosting configuration for Zope
Alan, I do something similar, but I do it with an access rule only (and adding a simple Site Root to each folder that has all properties blank)
Basically, I have an access rule that looks at the hostname (complete hostname, not just domain name) and then redirects to a properly named folder off the root.
Here is the access rule if you want to take a gander: <dtml-let virtual_dir="_.string.lower(_.string.join(_.string.split(_.string. split(HTTP_HOST, ':')[0],'.')[:],'_'))"> <dtml-if "virtual_dir != 'manager_host_com'"> <dtml-if expr="virtual_dir"> <dtml-call "REQUEST.set('SiteRootPATH', '/')"> <dtml-call "REQUEST['TraversalRequestNameStack'].append(virtual_dir)"> <dtml-else> <dtml-call "REQUEST.set('SiteRootPATH', '/')"> </dtml-if> </dtml-if> </dtml-let>
Basically, what this does is: 1. Grab the hostname, convert to lowercase (for those that are CAPS challenged) and then replace . with _ 2. Look and see if the hostname is the name of our management alias hostname (the hostname designated to be the Zope root, manager.host.com in this case) and if it is, simply do nothing and just continue on normally 3. If it's not our management hostname, then look and see if we have a folder that matches (IE: host_domain_com) 4. If we have a folder that matches, set our SiteRoot stuff, and add the path to the name stack
Simple solution really, and was done before the creation of VHM's in Site Access. I have several servers running with this solution and it works quite well.. The one drawback to this method is the case of wanting more than one site pointed to the same folder. Haven't figured out a complete solution for that yet ;-)
--Adam
On 21 Mar 2001 23:01:26 -0600, Alan Capesius wrote:
I've put together the following solutions for virtual hosting of domains and I'm looking for some feedback from the list.
The solution uses TinyTable, Virtual Host Monster and AccessRule and a DTML method to process all inbound requests by domain name similar to the way in which SiteRoot script things. The best part is that once set, the AccessRule does not need to be modified to add new hosts. Host to folder mapping is performed via entries in the TinyTable, the rest of the configuration is static. I would think it would be simple to implement something like this as a product, though it is beyond my current skill set.
participants (4)
-
Alan Capesius -
Bill Anderson -
Jonathan (Listserv Account) -
M. Adam Kendall