Hi Gaz, Unfortunately, I don't have any experience offhand with this particular configuration. I've submitted this as an Instiki bug (http://dev.instiki.org/ticket/348).
You could run Instiki behind Apache via a proxy config (e.g. Apache http://host:80/wiki/... proxies to http://host:3000/wiki/...). This can be quite snappy if you run Instiki with lighttpd instead of WEBrick. This arrangement is quite common on shared webhosting providers. You'll need to swap out Instiki's script/server with the stock one from a current rails install, as Instiki's script/server is a customized, pre-lighty script. If lighty's not an option, you could also try WEBrick in this setup to see if its performance is acceptable for your needs. -- John On Jun 1, 2006, at 8:23 AM, Gary Barlow wrote: > Does anyone host instiki v0.11.0 on Apache 2? > I understand this should be possilbe but can't get it to work! I have > Instiki 0.11.0 installed and have verified the install by running > it with > Webrick. I also have Apache 2 running other rails apps ok. > > I don't see much in the way of error logging. This is it: > > [Thu Jun 01 17:15:35 2006] [error] [client {ip}] Premature end of > script > headers: dispatch.fcgi > [Thu Jun 01 17:15:38 2006] [notice] mod_fcgid: process > /var/rails/instiki/instiki/public/dispatch.fcgi(13286) exit > (communication > error), terminated by calling exit(), return code: 255 > > Thanks Gaz > > > _______________________________________________ > Instiki-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/instiki-users _______________________________________________ Instiki-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/instiki-users
