Well for one going through Apache will give you the the ability to authenticate through apache which is able to authenticate using LDAP .... great for a corporate environment where people don't want to remember multiple passwords. I'm sure there are a few others but that's the first that comes to mind.
-Chris On Wed, Jun 4, 2008 at 7:26 AM, Michael Schmarck <[EMAIL PROTECTED]> wrote: > > Hello. > > I setup Trac on a (virtual) server, which will only host Trac. Right now, > I'm using FastCGI+lighttpd on that system and have it configured so, > that every request to / is served by the Trac FastCGI system. > > I'm currently pondering, if that makes sense to have it that way. > > Wouldn't it be easier to use the standalone tracd and have it serve > content on port 80, instead of lighttpd? Performance (speed) isn't > so important. > > What kind of disadvantages would I get, if I'd dump lighttpd (or > any other webserver, like Apache or whatnot) and would use > tracd directly? Again: That server will never host anything else > as Trac. > > Cheers, > Michael > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
