diff options
| author | https://id.koumbit.net/anarcat <https://id.koumbit.net/anarcat@web> | 2012-08-27 00:34:01 -0400 |
|---|---|---|
| committer | admin <admin@branchable.com> | 2012-08-27 00:34:01 -0400 |
| commit | 46ead22defecdba13f5ad5ddfd3e8bff8068f1e8 (patch) | |
| tree | bfc636d3a188b14a4019b1a9c25ecb703c58bbfb /doc/todo | |
| parent | 8f7fc90a9c92d8720a1455431f0f56d55b1fee2d (diff) | |
| download | ikiwiki-46ead22defecdba13f5ad5ddfd3e8bff8068f1e8.tar ikiwiki-46ead22defecdba13f5ad5ddfd3e8bff8068f1e8.tar.gz | |
explain how fastcgi could work. joeyh: this could help branchable.com's performance, i think (no idea if .cgi is a problem now...)
Diffstat (limited to 'doc/todo')
| -rw-r--r-- | doc/todo/fastcgi_or_modperl_installation_instructions.mdwn | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/todo/fastcgi_or_modperl_installation_instructions.mdwn b/doc/todo/fastcgi_or_modperl_installation_instructions.mdwn index 74dcaeb61..ad7910956 100644 --- a/doc/todo/fastcgi_or_modperl_installation_instructions.mdwn +++ b/doc/todo/fastcgi_or_modperl_installation_instructions.mdwn @@ -9,4 +9,10 @@ There has got to be a way to run the CGI wrapper under fastcgi or modperl (apach > I've not looked at what code changes fastcgi or modperl would require in > ikiwiki. --[[Joey]] +> > Looking at nginx support in [[tips/dot_cgi]], I had to figure that out, and it's not so complicated. The hackish way that's documented there right now (and also supported by [answers on serverfault.com](http://serverfault.com/questions/93090/installing-ikiwiki-on-nginx-fastcgi-fcgi-wrapper) or [other](http://vilain.net/comp/ikiwiki_setup.html) [guides](https://library.linode.com/web-applications/wikis/ikiwiki/arch-linux)), and involves starting up a fcgi wrapper, which I find personnally quite weird. +> > +> > Otherwise the general idea would be to launch a daemon per site that would have a pool of fastcgi processes to answer requests. The common setup pattern here is that users have a fixed quota of processes running as their user, listening either on the network (hackish: a port need to be allocated for each user) or on a socket (documented above, but then the webserver needs write access). +> > +> > Perl has had extensive support for FastCGI for quite a while. It seems to me a simple daemon could be written to wrap around the `.cgi`, it's a common way things are deployed. [RT](http://rt.bestpractical.com/) for example can run as a regular CGI, under `mod_perl` or `FastCGI` indiscrimenatly, the latter being more reliable and faster. They use [Plack](http://search.cpan.org/dist/Plack/) to setup that server (see the [startup script](https://github.com/bestpractical/rt/blob/stable/sbin/rt-server.in) for an example). But of course, [TIMTOWTDI](http://search.cpan.org/search?query=fastcgi&mode=all). --[[anarcat]] + [[!tag wishlist]] |