![]() Otherwise, you would have to ask your users to supply that information again and this is obviously not good for your work. There are so many reasons why you would want to store all the data and information you have.įor example, if you run a business or you have a blog platform you would want to store all your user’s information somewhere safe. Keeping these files could be for different reasons but most importantly, you want to store the file you worked on somewhere probably for future use or you might want to work on it again. Mostly when working we work with data and information that are supplied to us, and usually, when working with data or information supplied, there has to be a way to keep those files somewhere. Work that should ordinarily take a few days when it is was done manually can now be done within a few hours with more accuracy. It has better performance and is updated more often.Computing has made work easier to do compared to when things were done manually before. ![]() ![]() I would recommend going with XAMPP over MAMP. OSX's built in stuff might seem easier at first, but it's inflexible and eventually as your requirements grow you'll wish you hadn't done it. If you don't want to use MAMP i'd suggest getting a dedicated Linux box (or use a Linux Virtual Machine) to do this on having been down the OSX Apache path before. If you mess something up or need to quickly get different sites running with different settings it's kinda easier to blast things away in MAMP and start again (not that MAMP is without it's hassles). MAMP's daemons are easy to start/stop and your changes are confined to MAMP. If this is your primary OS, you are now running extra daemons (PHP/MySQL/Apache) in the background that eat up CPU cycles.If you wanted to enable PHP/MySQL etc later on you will be changing things in paths on the system that may break between OS updates.You can, it just feels hacky modifying stock system components). It's already there, you don't have to install anything.The answers to the SuperUser Question What is the best Apache PHP Setup for a Mac Developer talk about different MAMP, XAMPP, and roll your own solutions.I use git for version control and have a tendency to store source files in ~/developmentinstead of ~/Sites (this probably isn't material, but thought I'd mention it).I am interested in using virtual hosts in order to simultaneously develop multiple websites.If you're only developing static webpages and don't need PHP or MySQL, then why not use the built-in Apache with something like virtualhost-sh or VirtualHostX to ease configuration?.When not using the built-in Apache are there other benefits besides ease of configuration? For instance, is there a benefit similar to using virtualenv to avoid tainting a pristine Python install?. ![]() Is the advantage of a MAMP/XAMPP-based solution simply ease of configuration?.However, for some reason I just haven't wrapped my head around the benefits or potential pitfalls with using the built-in Apache versus using a MAMP/XAMPP-based (or other) solution. Instead of using the built-in Apache, I know that options such as MAMP and XAMPP exist. What are the advantages and disadvantages of using the built-in Apache for local web development on Mac OS X, specifically 10.6 Snow Leopard? ![]()
0 Comments
Leave a Reply. |