On Sun, Jan 17, 2010 at 1:48 AM, Sebastiano Pomata <sebastianopom...@tiscali.it> wrote: > After installing the package, pkg_add suggests to run the trac > standalone server, so I think I will stick with it for trac, while > keeping apache chrooted for other websites. > > I think my trac project it's simple enough that I don't need FastCGI > option > > Thank you
Sadly OpenBSD's Apache doesn't allow you to connect to an external FastCGI server if it isn't PHP. That would be super useful for things like this. Probably also a super security hole. The standalone HTTP server is probably your best bet. Or nginx. > > Il 16/01/2010 15.31, Stuart Henderson ha scritto: >> On 2010-01-15, Sebastiano <sebastianopom...@tiscali.it> wrote: >>> I found on OpenPorts the trac package, and I'm wondering if it is >>> already ok to work with chrooted apache provided by a default >>> installation. >>> >>> Or do I have to tweak something (or a lot)? >>> Or simply it just won't work and I should get apache-httpd? >> >> You'll have to copy a lot into the chroot (various parts of python >> and the associated system libraries). It can be done, but seriously >> weakens the chroot, and is a real pain to keep maintained. >> >> If you really want to run it as cgi, you can do this with base httpd >> using -u to disable chroot (optionally a second instance on a different >> port or address). >> >> I'm just using the built-in standalone server here though, it works >> fine for what I'm doing. If I wanted anything more complicated I'd be >> looking at the FastCGI configuration instead (but then I wouldn't >> be using apache either ;-) >> >> http://trac.edgewall.org/wiki/TracFastCgi > > -- Aaron Mason - Programmer, open source addict I've taken my software vows - for beta or for worse
