I simply experienced my self a brand new laptop, it operates on home windows 7 and i'm in deliberation what dev atmosphere to setup.
I've the majority of my existence used wamp setup, on home windows machines for local dev conditions. Here' lately installed IIS also it looks very convenient to setup sites and so forth and so on.
And So I am considering setting up php and mysql and runing local dev atmosphere via IIS. Now you ask , like me a newcomer to IIS. What are the draw backs to running php/mysql via IIS in local dev atmosphere. What exactly are my restrictions, will running php/mysql create any restrictions if any which will hinder development and can effect deployment.
In each day i'd some contact with ISS with php running on server, it had been very long time ago, but php wasn't completely supported plus some dev issues came about.
Thank everyone for just about any input. Greatly appreciated.
Usually it's a benefit if you're able to use identical conditions for development and production. So now you ask ,:
On which stack would you deploy you programs?
I'd choose Apache - mainly for that .htaccess functions - spinning etc are a little more tricky in IIS and you'll not get as great portability when transfering to some Light setup.
Personally, i think that apache on home windows continues to be a much better means to fix develop PHP. Reasons:
- a lot more documentation concerning the interaction between PHP and apache (for instance url spinning, proxying, etc...)
- apache may be the p-facto standard for PHP, if you intend to deploy to apache later, you'll face less potential issues because of platform variations (also concerning the rare subtle bugs which could plague ported software)
- I've found it simpler to obtain significant error messages from apache than from IIS
I attempt to set up exactly the same PHP and Apache versions I'll be implementing to, therefore the chances to possess variations is minimal...