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 :-)