![]() ![]() dev domains, that's something you always manage on your host system, not the VM, so your hosts file must redirect your desired. The actual files/folders in the Apache are symlinks to folders on your host system, so no worries if you f*ck up the VM, just reinstall with the given config, piece of cake. It's a bit of a learning curve, but then it's great. I think this is a great start when beginning to learn programming for the web - so no need at all for most beginners to even bother with this topic here -).There are predefined server images with predefined configurations out there in the web, just search for it. I truly respect that, and your actually made me learn more about MAMP, thx! :-)Īnd last but not least, here at treehouse there is still the "workspaces" you can use doing most of the courses content. *Since XAMPP 5.6 MySQL is replaced by MariaDB this might also be considered (use of PDO in PHP. This would be indeed a strong point for people using Mac, although not sure if the new DBMS (MariaDB*) on XAMPP produces the same issues. Probably the most important for me personally, low memory and CPU usageĪs far as I know this is a Mac-related (not PC) problem with "mysql". ![]() Like you suggested, this should preferably be done in testing environments that simulate production servers environment (e.g. The ability to easy test production-like settings without needing to manually change files ![]() By the way, does MAMP also support PHP 7 at the moment (March 2016)? ![]() I think both applications are intuitive enough to quickly click and switch on/off Apache and MySQL (now MariaDB*). Supposing that GUI and installation process on MAC and PC are similar (with Linux your bound to XAMPP anyway), I think there is not much differences in the ease of use if you just need to set up a local web server working on a web page on your local computer.Īn intuitive UI with lots of configurable options for Apache, PHP and MySQL Just some comments on your listed statements in your reply: Others here, including you, made it clear that you where talking about the commercial version "MAMP pro" in you first replay stating that it is a more advanced development environment. Maybe I was a bit provocative with my first statement. I didn't pay because it was already done, but because it saves a lot of time if I need to format my MacBook as the backup contains all vital data about virtual hosts, PHP versions and settings, SSL certificates etc.Īgain, these opinions are my own based on software evaluations over the past 6-7 years. or you pay 40 bugs and get it mostly done in MAMP pro (like others think you might need it in most cases). Yes, it would give you a better understanding but it would be far better to do so within a Linux VM where the environment would be more predictable when getting set up. Getting multiple versions of PHP working isn't a trivial process since it requires intermediate knowledge of setting up PHP-FPM and FastCGI, of course there are plenty of tutorials - but it's a slow and frustrating process for someone who has never set it up before. Probably the most important for me personally, low memory and CPU usageĪnd having a sever use different PHP Versions and virtual hosts (different webserver configuration in one) require either a little configuration your self (which by the way gives you a better understanding how a webserver works).The ability to easy test production-like settings without needing to manually change files.An intuitive UI with lots of configurable options for Apache, PHP and MySQL.Yes, the underlying technologies used by MAMP and XMAPP are pretty much the same, I look past that for: I assure you I am not a reseller, I have tried several different options to local stacks on OS X but all have fallen short of MAMP in my personal opinion. Hey Chris, sorry that I am so curious but you sound like reseller of the MAMP pro Version. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |