![]() +ipc - Building a site with high-performance demands? +sqlite - Nice light-weight database engine +postgresql - Nice transactional database. +snmp or +macports_snmp - Network monitoring and management +fastcgi - Probably not needed for development servers +apache2 or +apache (Apache 1.3) - We're installing the apache2 module ![]() In addition to these extensions you may add the following variants: MacPorts enables several key extensions by default, including curl, freetype, jpeg, libpng, libmcrypt, libxml2, libxslt, mhash, and tiff. Warning: apache2 requests to install files outside the common directory structure! # sudo launchctl load -w /Library/LaunchDaemons/ Execute the following command to start it, # A startup item has been generated that will aid in Here's the tail of my installation's output. Install Apache 2 by issuing the following in a Terminal window (add variants, if desired): +no_startupitem - Include this if you don't need to start Apache at system boot. Review Apache documentation on each if you're building a server to handle a lot of traffic. +preforkmpm, +workermpm, +eventmpm - I grouped these together because they're related to server process management. +openldap - Provides LDAP authentication features. There aren't many port variants for Apache 2, and those that exist are probably not needed by most developers. It's easy to switch back and forth between stock- and MacPorts-Apache instances, but running both at the same time, without changing network port settings, will cause problems. Important: To avoid conflicts with the stock Apache installed on your Mac, turn off Personal Web Sharing under the Sharing System Preferences pane. If you have MacPorts and your database of choice installed, let's get started. I hope to try LightTPD sometime but for now I'll stick with Apache simply because I'm comfortable configuring and administering it. LightTPD does not consume the CPU cycles or memory that Apache does and looks like an efficient alternative. ![]() I've read great things about LightTPD, a light-weight HTTP server. If you're going to develop site's against a database, might I suggest installing MySQL. If you haven't already done so, install MacPorts. Use MacPorts to install Apache 2 and PHP 5 Install everything but the kitchen sink with MAMP or XAMPP Use the stock Apache 1.3 with a PHP package, like the one from Here are a few of the options Mac users have to set up a PHP development environment: I'll mention a few of the other options and then share the steps I've used to install Apache 2 and PHP 5 with MacPorts. While options abound, MacPorts may be the easiest option to configure a local web development environment on your Mac. The steps should now work for Leopard as well as Tiger. There are several sections in the MacPorts Guide that also describe the process of using leaves to uninstall unneeded ports.4/2/08 - Added php.ini settings to use the proper MySQL socket at /tmp/mysql.sock.ģ/23/08 - After going through these instructions on a new Leopard system, I made a few minor updates. ports that are dependencies of ports that are installed, but inactive): sudo port uninstall inactive Note: Before pruning your leaves, you may also want to uninstall old versions of ports that are no longer “active”. You can uninstall any remaining leaves quite easily: sudo port uninstall leaves Some common leaves ( automake, gperf, libtool, pkgconfig) are build-time dependencies of common ports, so you may want to “request” them ( sudo port setrequested port1 port2 port3 …) to avoid uninstalling them just to have to reinstall them later. You should examine your existing leaves before uninstalling any of them. You can use this to “clean up” unneeded ports even if you did not originally uninstall them with sudo port uninstall -follow-dependencies portname (which will do what you want, but only if you remember to use it every time you uninstall something). The leaves pseudo-portname expands to all the unrequested ports upon which no other installed port depends. An unrequested port is one that was only installed because some other port depends on it. One of the features of the new format is that it keeps track of “requested” versus “unrequested” port installations. You can convert a 1.9.x flat system to the sqlite format by upgrading to MacPorts 2.0 or by changing the portdbformat value in /opt/local/etc/macports/nf and then issuing a port command as root (e.g. The sqlite port DB format is the default for new installations old installations that were upgraded to 1.9.x will continue to use the flat format 1. MacPorts 1.9.0 added the sqlite portdbformat and MacPorts 2.0.0 dropped the old flat format. To avoid accidentally cutting leaves that might be things you requested you should install the port_cutleaves package then run sudo port_cutleaves
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |