On Mon, Nov 05, 2007 at 07:02:05PM GMT, Alexey Zakhlestin [EMAIL PROTECTED]
said the following:
> Did you just ignore the part about fastcgi?
>
No I didn't, I just feel that fastcgi/suexec/mod_suphp doesn't handle
all of the ready to run programs out there completely. Besides that, the
whole point of PHP was that it was made to be part of Apache originally,
so why not just have us all write Perl scripts?
See, my problems with PHP setups come down to this:
A. I could run PHP without safe mode and only have open base dir on
and be wide open for breaches.
B. I could run mod_suphp/suexec/fastcgi for everyone and then certain
programs would not run right. Performance would take a bit of a
hit. People would say "Why are you running it like that, you're dumb,
etc." My impression of this scenario is based on a few years old
information, testing and perhaps not enough research so maybe I should
look into this method again.
C. I could use the metux MPM, but then I couldn't do SSL, which means
no ecommerce sites.
D. I could run things the way I have it now, but that won't last
because PHP 6 is on the way.
E. I could run Apache chroot and have 50 instances of Apache running
on a server. Performance would no doubt take a hit, even with
lots of CPUs and RAM. I have also planned for about 200 users per
server so I'd be losing a lot that way. Complexity would go way up as
well as management time and I'd have to deal with users messing up their
chroot environments.
F. Try to get the mpm-itx setup working, but that's an unknown right
now.
I should have taken that sign more to heart that I read one time:
"Formula for failure: Try to please everybody".
Mark
--
Mark S. Krenz
IT Director
Suso Technology Services, Inc.
http://suso.org/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
