Date: Thu, 17 May 2012 10:38:37 +0200 From: Jeremie Le Hen <jlh@FreeBSD.org> To: tzabal@it.teithe.gr Cc: Ilya Bakulin <webmaster@kibab.com>, freebsd-hackers@freebsd.org Subject: Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion Message-ID: <20120517083837.GB16038@felucia.tataz.chchile.org> In-Reply-To: <20120516144524.19813u8j0pnxpbh0@webmail.teithe.gr> References: <20120516003020.82068pr8h9dyqjfw@webmail.teithe.gr> <4FB34CF0.6000306@kibab.com> <20120516144524.19813u8j0pnxpbh0@webmail.teithe.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 16, 2012 at 02:45:24PM +0300, tzabal@it.teithe.gr wrote: > > In this case Apache is a good choice. I would however recommend using > > www/nginx and PHP in FastCGI mode (FPM option in lang/php5 port). This > > is a preffered setup for almost all Russian highloaded websites. > > At the beginning using Apache is a reasonable choice. > > I have never used nginx before. I have considered also the lighttpd. > Both with BSD licenses (nginx with a 2-clause BSD like license) and > FastCGI support. As I read from Wikipedia, PHP performance has > received special attention in lighttpd. I will test both Web servers > and then I will make up my mind. I think the HTTP server is not a big deal unless there is a really useful feature in one that the other doesn't provide. Most of the work will be done by the PHP backend anyway. >From an architectural point of view, best practices nowadays are leaning toward external PHP processes with FastCGI, as described by Ilya. There are alternatives to FPM, such as sysutils/py-supervisor. I don't know who will be administrating this server in the end, but I think it would be good to ask the FreeBSD webmaster team opinion though. -- Jeremie Le Hen Men are born free and equal. Later on, they're on their own. Jean Yanne
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120517083837.GB16038>