[Tracker-discuss] Roundup installed
izak at upfrontsystems.co.za
Sat Nov 11 07:18:52 CET 2006
Roché Compaan wrote:
> It is running at http://psf.upfronthosting.co.za/roundup/meta/ and you
> should be able to register as a user.
config.ini needs a few more tweaks. The mail comes from the wrong
address at the moment for example...
> Submitting issues via the web doesn't work at the moment due to a
> permission error. This reminded me why we prefer using the roundup
> server - it can run as the roundup user and it saves you the hassle of
> permissions dances with Apache. Mail delivery works fine.
I'm thinking of this: http://httpd.apache.org/docs/2.0/mod/perchild.html
> mod_python scripts should also be executing as the roundup user but the
> SuexecUserGroup directive is ignored at the moment (most probably
> because of restrictive compile options that we are violating). We need
> to checkout the debian compile options for Apache.
suexec only works with actual cgi scripts.
> As far as responsibilities on the server goes, my feeling is that we can
> all help. It is probably simpler if we (Upfront Systems) look after the
> maintenance and security of the server and the rest of the
> administrators look at roundup. We would like to help with Roundup as
> far as we can though. We can coordinate the effort using a tracker but
> let's spell this out in another thread.
> Any questions about the current setup are welcome.
One other thing that isn't clear to me. With the mod_python example in
the documentation (I added a rewrite rule to redirect to /roundup/)
there is no way to get an index page, ie a list of the hosted trackers.
The builtin server does this if you have more than one tracker and
don't specify a specific one. How would you make a mod_python setup do
the same? Or should we simply use a static index page that needs
updating whenever a new tracker is added?
More information about the Tracker-discuss