osx - Advantages/disadvantages of using the built-in Apache for web development on Mac OS X -
10.6 Snow leopard especially on the advantages and disadvantages of using embedded Apache for local web development Are you
Rather than using the built-in Apache, I know that the options exist and exist. However, for some reason I have not wrapped my head around profit or potential damage with the use of Apache vs. built using MAMP / XAMP based (or other) solution.
- Does the benefit of the MAMP / XAMPP based solution easily ease the configuration?
- While not using the built-in Apache, there are benefits other than ease in configuration? For example, is there a benefit to using VirtualNV?
- If you are developing only stable webpages and you do not need PHP or MySQL, then why not create Apache with something or
Configuration and usage related issues
- I am interested in using virtual hosts to develop many websites together
- I use git for version control And source files in
~ /
instead of~ / sites
There is a tendency to store (this is probably not content, but I think I want
related research
- Super MSP, XAMPP About the Superuser question and roll your own solution
Benefits :
- It's already, you do not have to install anything
- If you are explaining, there are only .html files , So it's okay.
Disadvantage:
- You can not update it (okay, you do not want if you If you want to enable PHP / MySQL etc., then you will want to change some things in the paths on the system that can break between OS updates.
- li>
- If this is your primary OS, then you are now running additional daemons (PHP / MySQL / Apache) in the background that eats the CPU cycle.
Overall though I do not do it, it's easy to start / stop the demons of MAMP and your changes are limited to MAMP. If you do something wrong or need to get different sites running with different settings, then it looks easy to remove things in MMP and starts again (not that MAMP is without its barriers).
If you want to use MMP, I recommend using a dedicated Linux box (or using a Linux Virtual Machine ) before dropping the OSX Apache path It was not easy for OSX stuff to be easier than before, but it is inflexible and ultimately with your needs increasing, you want you did not do that.
Update: I would recommend going to MAMP with better performance than XAMPP and updated more frequently. Plus XAMPP is cross platform and open source :)
Comments
Post a Comment