Iis + php

[Solignis]

I am attempting to install IIS and PHP on my email server so I can host out a website called RoundCube Webmail.

My email server is based on windows, it is called hmailserver.

I am running hmail with MySQL Community 5.1.

I went to download PHP for Windows and found myself at a fork in the road.

I have 2 choices on types of PHP to download.

Either Thread-Safe or Non-Thread-Safe. What is the difference?

I read something on wikipedia about thread safety, but I am still lost.

While typing this I just downloaded both of them, but I am not sure which one to install.

[mdh]

Read this:

http://www.iis-aid.com/articles/my_w..._safe_binaries

In a nutshell, its about connections to the database sharing threads, the robustness of the method (in general), the other code in use, the apps in use, and (likely) whether its in a protected area or accessible to the outside world. You can do a bit of reading and hopefully know what's best for you.

[Solignis]

my head hurts and I have just began my journey down the php road.

[sky-knight]

PHP + IIS = Unstable

I don't care how much work you put into it. We've already had this discussion over IM. :P But to be honest, all you really have to do is get the latest PHP windows installer and double click. It does it all for you.

[Solignis]

Yeah I know we have discussed this, but seeing from where I stand I am very limited on options. I would go the easy way and just use something like WAMP or XAMPP but I don't need the MySQL server and the last time I remember you can't select what you want to install. Or maybe you can I don't recall.

[Solignis]

Well I feel silly, I went and tried to install AppServ. Which is my personal preference in Apache, MySQL, PHP packages. It allows me to select which parts I want.

In terms of ease of use, Apache is more straight forward than IIS isnt it?

If I am omitting MySQL from the package installation, is there anything I must do to PHP to make it work with the MySQL server I already have installed? Or is it not dependent on the SQL server?

[Mathiau]

Originally Posted by sky-knight

PHP + IIS = Unstable

I don't care how much work you put into it. We've already had this discussion over IM. :P But to be honest, all you really have to do is get the latest PHP windows installer and double click. It does it all for you.

not %100 true, maybe 6-7 years ago when it was poorly ported over to work on windows but today it is stable, now it may have better performance on linux, but that is another story.

use fastCGI for server 2008.

we have been using PHP+IIS for 8 years with no issues of stability for any of our reporting systems or hosted site, i am sure this is one issue that can go back and forth, a system is only as good as the person who set it up.

IIS is more straight forward because of the GUI, Apache is all text based to edit settings, not that it is hard, i administer 3 apache based severs and 2 IIS 7 ones, people will argue Apache +php+mysql should only run on Linux blah blah blah, but it runs fine on windows also.

i found IIS is far easier to configure for virtual hosts then apache is

the easy way and just use something like WAMP or XAMPP

Unless you secure it down, don't even think of using them on public facing sites, the sites say themselves they are for testing only, because all modules and add-on's are loaded by default.

PHP + IIS7 fastcgi
http://www.jppinto.com/2009/03/insta...s-server-2008/


MYSQL + PHP and IIS7
http://maximumpcguides.com/windows-v...hp-web-server/


For MySQL you need to uncomment the...\

extension=php_mysql.dll

some guides also say to un-comment

;extension=php_mysqli.dll
;extension=php_mbstring.dll

[sky-knight]

FastCGI is an entire can of worms in and of itself. I've had it working on a few IIS7 implementations and seen the thing break with random security patches.

The problem is, no matter how you want to slice it. PHP was designed to work within the linux realm of thinking. Windows is very different, and operating it there always requires a certain amount of translation. That translation process is rife with security issues, and performance issues.

If you want to run PHP on a windows server, just get the windows version of Apache 2 and build from there. At least then you aren't dealing with IIS's CGI deficiencies. Finally, virtual hosting with Apache 2 is trivial. I have a .conf file for each domain I host, and each one is identical. I wrote it once... all I do now is copy and paste the thing and change the domains out. One day I'll get unlazy and write a script that creates the conf file for me.

P.S. I need to clarify here... I'm not knocking IIS7, it's a wonderful web service and the only portion of server 2008 I really do like. I just believe in using things for what they are designed for. IIS is for .NET, Apache is for PHP.

[Mathiau]

i cant disagree with you there, i am glad i haven't hit any of the issues with security patches, could be we just don't use enough of PHP's abilities to run into any major issues.

The last time i had tried to do virtual directories with Apache was about 2 years ago and i just gave up as i could not get it to work, nor could my work m8 (sure it was our error), went to IIS, add Virtual site, done, include headers, done.

I will say getting php+mysql to work with Apache is a HECK of a lot easier then any IIS install i have had to do!

[sky-knight]

You should give a base Debian installation a try. They've separated the Apache configuration up into a directory format that is very intuitive. They provide templates for a generic port 80 virtual host, you can modify that to suit your needs and copy it as many times as you want for new virtual hosts.

No it isn't as brainless as IIS thanks to Microsoft's very well done GUI. But once you get used to it you'll find yourself disliking IIS because it takes too long to drill down to the setting you want.

And, while you're at it you'll be getting better at the same base OS Untangle operates on, improving your ability to support and maintain Untangle servers.