Noah Kantrowitz wrote: >> -----Original Message----- >> From: [email protected] >> [mailto:[EMAIL PROTECTED] On Behalf Of Chris Nelson Sent: >> Thursday, August 28, 2008 11:44 AM >> To: [email protected] >> Subject: [Trac] Re: 403 errors trying to access trac >> >> >> Noah Kantrowitz wrote: >>> /me repeats yet again. >>> >>> Do Not Use CGI. Period. >> >> Would I face different problems if I used FastCGI? It seemed CGI was >> the shortest route to getting the basic application working. I >> expect to migrate to FastCGI later but I don't have a FastCGI module >> in my Apache server yet. > > Install one of FCGI, mod_python, mod_wsgi, etc and use that if you > want to use Apache. If you want the fastest way to get things > running, you want to use tracd.
By "fastest way to get things running" do you mean the shortest route to a working system or a working system that is the fastest in use? IAC, will tracd allow me to have trac and gitweb available on the same server? I take it there's somewhere I bind tracd to some alternate port (besides the 80 that httpd is listening on)? Apache is the way someone else got gitweb working on this server but I don't care much how I implement trac. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
