For everyone, how do you feel about changing QMT's apache dependencies
to nginx? (Long term - this isn't going to happen over night)
Note, http related .qt. packages are not part of the 'core'
(operational) QMT components. A QMT host can function fine without any
of these packages (e.g. qmailadmin, vqadmin, isoqlog, etc.).
I'm not suggesting we drop http functionality. Far from it. I'm merely
suggesting that nginx might be (is likely to be) more suitable in the
future as a http server component for QMT than apache is. nginx is very
efficient, and much easier to configure. The ease of configuration may
likely (imo) pay dividends down the road.
I already run SquirrelMail on its own (virtual) PHP server, augmented by
an nginx (virtual) (reverse-proxy) web server. It works quite nicely,
and separates the webmail component entirely from the base mail server.
I'm under the impression that fastcgi can run qmailadmin and vqadmin (C
stuff) as well as PHP code. If that's indeed the case, other QMT
components could be adapted in a similar manner. Of course, separate
hosts wouldn't be required. It would just be an option which allows
separation (and scaling in a big way).
So what are your thoughts?
Thanks.
--
-Eric 'shubes'
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
