scripts / trac / andersk 01:47 (Anders Kaseorg)
There’s nothing stopping us from redirecting scripts.mit.edu/~locker
to locker.scripts.mit.edu. But that doesn’t imply that
locker.scripts.mit.edu/~locker should stop working.
scripts / trac / andersk 01:48 (Anders Kaseorg)
scripts/~locker and locker.scripts/~locker are already being served
through two _totally_ different mechanisms.
scripts / trac / geofft 02:14 (apt-get install wnpp)
I guess what I'm saying is... if I'm setting up my own non-scripts
server, and I want both trac.example.com/ and example.com/trac/ to
work, do I need to configure some /_var_www/ magic directory that
exists on both?
scripts / trac / andersk 02:15 (Anders Kaseorg)
Where trac.example.com and example.com/trac refer to the same
directory in the filesystem? I think so. I would love to be proven
wrong.
scripts / trac / andersk 02:15 (Anders Kaseorg)
(You can do it with httpd.conf instead of .htaccess, but that’s not
the point here.)
So I guess this bug is "figure out if that /_var_www/ claim is wrong, and if so, use that knowledge to make all the autoinstallers much prettier".
A related issue is "document what /~locker does".
