and that generally make a mess of things.Īnd at the end of the day, those people would rather install and configure Apache, PHP, and MySQL their own way. The main reason is that some people have had a negative experience using a "everything including the kitchen-sink" type WAMP distributions that comes with a FTP Server, Mail Server, JSP Server, DNS Server, have issues with upgradability, security. If the question is - using Windows as my platform, why would some people tell me to install Apache, PHP, and MySQL separately rather than as part of a WAMP distribution. When you install a LAMP stack from your distribution's package repo, everything will be in an expected, well-known location. As such, when you (or anyone else) go to troubleshoot things, you're left searching all over your filesystem for, say, your php.ini file. In the vast majority of the time, you're able to upgrade everything with a single command.įinally, #3: one-click installers place their files in very non-standard locations. When their packages get released to their official repos, they've been through much testing and the chances of them breaking anything on your system are fairly low. Then, for #2, OS vendors make it very easy to keep your LAMP stack upgraded with the most recent feature updates and security patches. This is OK for development work, but incredibly stupid to do in production. As such, many of the configuration values are intentionally left in a very insecure state. are designed to be one-click stack installers that make it easy for developers to get to work quickly and with the least resistance possible. To expand on #1: WAMP, MAMP, LAMPP, XAMPP, etc. There are many differences, though the three most troubling ones are: Since a WAMP stack itself is composed of apache, mysql and php, then what's the difference between using the WAMP stack and installing them all separately?
0 Comments
Leave a Reply. |