Zope port and provider
Hi all a friend of mine fired this question at me can someone help me give him a awnser? "There appears to be a serious flaw with zope: one needs a zope provider. and there aren't too many. apparently zope grabs port 80 and keeps it. is this true? are there workarounds so that any isp will do?" I know there are quite a few Providers. Hope someone can help me. Greetz, Jamez
On Tue, Nov 27, 2001 at 04:41:36PM +0100, James van der Veen wrote:
"There appears to be a serious flaw with zope: one needs a zope provider. and there aren't too many. apparently zope grabs port 80 and keeps it. is this true? are there workarounds so that any isp will do?"
Not true on unilaterally grabbing port 80. It'll grab whatever port you tell it to (and doesn't default to port 80), and you can selectively enable/disable Zope's http, ftp, and webdav services. Some (like me) run Zope as a separate process listening on a high-numbered port, then use Apache or Squid as a proxy server to direct particular requests (or all requests) to the Zope process. A provider that gives you shell access or at least the ability to run your own daemons, and a bit of tweaking to the section of their httpd.conf is all that's required. You can avoid the httpd.conf tweaking if you don't mind having URLs with ugly port numbers in them. Some use the PCGI method of running Zope, which should work with any web server that does PCGI (definitely Apache, and probably IIS). Don't know if there's any reduction of effort on this compared to the previous solution. The insane (or those who expect almost zero Zope traffic) run Zope as a regular CGI, instead of as a persistent CGI. Any provider that lets you upload your own CGIs should be compatible with this, but it'd be incredibly slow under load. -- Mike Renfro / R&D Engineer, Center for Manufacturing Research, 931 372-3601 / Tennessee Technological University -- renfro@tntech.edu
Hi all a friend of mine fired this question at me can someone help me give him a awnser?
"There appears to be a serious flaw with zope: one needs a zope provider. and there aren't too many. apparently zope grabs port 80 and keeps it. is this true? are there workarounds so that any isp will do?"
it is very well possible to put zope behind Apache. By using persistent CGI, it is not too hard to get this working. Since much of the commands you need in the httpd.conf can also be set in .htacces, this wil most likely also be possible when you are on a shared Unix webserver (were you cannot change the httpd.conf). (I have such an experiment on my todo list ";-) There are several howto's available to get this working. Since you are in the Netherlands, another option for you might be hosting at amaze.nl, they do Zope hosting. Reinoud
From: "James van der Veen" <james@codenamefuture.nl>
"There appears to be a serious flaw with zope: one needs a zope provider.
Uhm, no, you can run Zope yourself too, no problem. But yes, as with every website, you eother need a leased line, or a webhotel. Zope hotels are less common, thats correct. http://imeme.net/ is supposed to be really good.
apparently zope grabs port 80 and keeps it. is this true?
Not at all. What port it should use is completely configurable.
participants (4)
-
James van der Veen -
Lennart Regebro -
Mike Renfro -
Reinoud van Leeuwen