Re: [Zope] Zope for 200 users?
I'm going to setup Zope 2 on a machine with about 200 users (now using Apache). I don't know how many are going to use Zope.
Ah, the concept of 'users' go away on the Web, quite honestly, given it's grand stateless architecture. *gack*
I'd like to use Zope trought Apache. Each user should have his ressources un his home dir (e.g. /~user/zope/).
If you mean all their objects get stored here, then well, you're not going to like the answer, because at this point Zope doesn't have the ability (at least not exposed) to combine a bunch of object databases into one tree.
Now my Question. Do I have to start a z2.py for each user (Described in http://www.zope.org:18200/Members/jec/virtual_howto_html) or is there a better solution?
If you want to store it that way, yes. Now if you just want to MAP /~users/zope/foo to user foo, and such, then that's fine. Starting a Zope for each user would be insane :-) Chris -- | Christopher Petrilli Python Powered Digital Creations, Inc. | petrilli@digicool.com http://www.digicool.com
Just tested the following Apache RewriteRule. It maps www.your.site/~dinos/zope/x to http://www.your.site/public/people/dinos/x Only tested several URLs, so it might not work well for you, but I do not see any reason It will not work well. In this case, www.your.site/public is the URL root zope folder. people is the subfolder of your zope root folder in which you put the folders for your *users*. As usual RewriteRules are one-liner. RewriteCond %{HTTP:Authorization} ^(.*) RewriteRule ^/~(.*)/zope/(.*) /home/httpd/cgi-bin/public.cgi/people/$1/$2[e=HTTP_CGI_AUTHORIZATION:%1,t=application/x-httpd-cgi,L] RewriteCond %{HTTP:Authorization} ^(.*) RewriteRule ^/public/(.*) /home/httpd/cgi-bin/public.cgi/$1 [e=HTTP_CGI_AUTHORIZATION:%1,t=application/x-httpd-cgi,L] LKS BTW, on the pronunciation of Zope: 'Zope' in vulgar-Latin-style-Korean pronunciation(something like Joe-Pae) means 'to beat someone to the jelly'. So it made a perfect pun for those forced to use Zope by me. ;-). For it is very hard for them to distinguish files in local hard from those in the server.
I'm going to setup Zope 2 on a machine with about 200 users (now using Apache). I don't know how many are going to use Zope.
If you want to store it that way, yes. Now if you just want to MAP /~users/zope/foo to user foo, and such, then that's fine. Starting a Zope for each user would be insane :-)
On Tue, 24 Aug 1999, [Windows-1252] ÀÌ°ü¼ö(LEE Kwan Soo) wrote:
Just tested the following Apache RewriteRule. It maps www.your.site/~dinos/zope/x to http://www.your.site/public/people/dinos/x Only tested several URLs, so it might not work well for you, but I do not see any reason It will not work well. Well, just do a REQUEST dump, then you will notice that ZOPE believes to be in quite a different place than the URL the browser shows :(
If it were so easy, subsiting ZOPE would be trivial ;) Andreas -- Andreas Kostyrka | andreas@mtg.co.at phone: +43/1/7070750 | phone: +43/676/4091256 MTG Handelsges.m.b.H. | fax: +43/1/7065299 Raiffeisenstr. 16/9 | 2320 Zwoelfaxing AUSTRIA
participants (3)
-
Andreas Kostyrka -
Christopher Petrilli -
ÀÌ°ü¼ö(LEE Kwan Soo)