On 30 May 2010 02:59, Richard Hipp wrote:
>
> "CGI ... is highly inefficient". The http://www.sqlite.org/ and
> http://www.fossil-scm.org/ websites are both run off of the same server
> (check the IP addresses on the domains). The HTTP server there is a simple
> home-brew job implemented as a si
On Sat, 2010-05-29 at 21:59 -0400, Richard Hipp wrote:
> The http://www.sqlite.org/ and http://www.fossil-scm.org/ websites
> are both run off of the same server ... This server takes over a
> quarter million requests per day, 10GB of traffic/day, and it does
> so using less than 3% of of the CPU o
On Sat, May 29, 2010 at 7:21 PM, Owen Shepherd wrote:
> We are currently experimenting with setting up a Fossil server, but have
> encountered a bit of an issue: Fossil doesn't seem to support being operated
> behind a proxy. As we wish to run Fossil on port 80, and to do so it must
> sit behind
On 30 May 2010 00:53, Michael McDaniel wrote:
> I wound up running lighttpd for the sole purpose of serving fossil
> via cgi scripts. lighttpd is pretty lightweight on resources.
>
> ~Michael
>
The idea has crossed my mind, but the idea of having to maintain another set
of configuration files
On Sun, May 30, 2010 at 12:21:50AM +0100, Owen Shepherd wrote:
>We are currently experimenting with setting up a Fossil server, but
>have encountered a bit of an issue: Fossil doesn't seem to support
>being operated behind a proxy. As we wish to run Fossil on port 80, and
>to do so
We are currently experimenting with setting up a Fossil server, but have
encountered a bit of an issue: Fossil doesn't seem to support being operated
behind a proxy. As we wish to run Fossil on port 80, and to do so it must
sit behind our primary web server, this is a bit of an issue.
The ideal so
6 matches
Mail list logo
