Well, folks, I’m back from Summer Film with a vengance. And it’s time to get down to some programming, so here goes.<\/p>\n
We’ve all heard about Ruby on Rails. “It’s so great,” they say. “Ruby is so simple, and efficient,” I hear. “There’s a cool guide that has Foxes<\/a>!” says some other guy from the back.<\/p>\n <\/p>\n But I already know PHP. I like PHP. In fact, I really<\/span> like PHP. It has that old-school C style syntax, and yet, it’s just frustratingly different enough from C to make it enjoyable to code in. (I use 4; 5’s good too, but I haven’t bothered to seriously update, because my hosts still use 4 on the majority of their boxes, including the one I’m on.)<\/p>\n So what great MVC package is there for PHP similar to Rails for Ruby? Well, there’s PHP on Trax.<\/a> A plus is that it fairly closely follows Rails. But, it requires PHP 5. Hmm. Yeah. 5’s great, but no thanks right now.<\/p>\n There’s also TaniPHP<\/a>, which supports PHP 4. But that’s not been updated in ages, and it looks like it won’t be.<\/p>\n And then there’s CakePHP<\/a>. PHP 4 support, check. Inspired by Rails, check. Good documentation, check. Active community, check. Fantastic.<\/p>\n So here’s my adventure installing CakePHP on Mac OS X. You can follow along, if you like.<\/p>\n Step Zero:<\/span> So here’s the easy way: Marc Liyanage’s OS X Packages<\/a>. Easy, helpful, just follow his instructions.<\/p>\n Step One:<\/span> The latest stable version at the time of this writing is 1.1.5.3148. Go ahead and download it from CakeForge<\/a>. Once you’ve unzipped it, rename the resulting folder “Cake” and move Cake to \/Library. Now you’ll have your Cake Libraries installed in \/Library\/Cake. Recursively delicious.<\/p>\n Step Two:<\/span> Step Three:<\/span> I like working out of my home directory, though. Fortunately, Personal Web Sharing also enables the Sites folder of my home directory to serve files: http:\/\/localhost\/~myhomedir\/. Using the blog example, I’ll typically move the webroot folder (in \/Users\/myhomedir\/app) to \/Users\/myhomedir\/Sites, and then rename it ‘blog.’ Now, my Cake blog will be served from http:\/\/localhost\/~myhomedir\/blog\/. Flexible, and handy.<\/p>\n Step Four:<\/span> Going back to the blog example, let’s review: First, modify the index.php file in your webroot. Look for the comment box that talks about Cake being installed in a directory layout different from it’s distribution. Modify the code like so:<\/p>\n Now Cake knows where to find it’s library and application files.<\/p>\n All that’s left is to setup the database connection. Easy peasy: go to the application directory (\/Users\/myhomedir\/blog). You’ll see a “config” folder. Within that folder, duplicate “database.php.default” and rename the copy database.php. Open up this file in your text editor of choice (I like jEdit<\/a> as far as programming, by the way).<\/p>\n Cake is nice in that you can be simultaneously running a few databases in order to have a ‘testing’ environment and a ‘default’ environment. Since this is just a development box, I generally just modify the default array. For this setup, you need only change the “login”, “password,” and “database” values to their appropriate MySQL values. For example:<\/p>\n Step Five:<\/span> That’s all there is to it. You’re ready to code up the Blog tutorial, or start your own application. And a big plus is that for any major Cake changes, you can just install the new libraries into \/Library\/Cake, without having to change your application code!<\/p>\n Out.<\/p>\n","protected":false},"excerpt":{"rendered":" Well, folks, I’m back from Summer Film with a vengance. And it’s time to get down to some programming, so here goes. We’ve all heard about Ruby on Rails. “It’s so great,” they say. “Ruby is so simple, and efficient,” … Continue reading
\nInstall PHP and MySQL for OS X. I did this a long time ago, but if you’re just getting started, you’ll probably like to do this. Otherwise, things are really not going to make sense later. There are great instructions for installing PHP & MySQL by hand on Apple’s Developer Connection<\/a>, but I’m not setting up a production box, I’m setting up a development box. For that, I do things the easy way. I’ll optimize later.<\/p>\n
\nDownload and unzip Cake. Because I’m developing multiple Cake apps, I’m going to put the resulting directory in my \/Library (that’s Root Library. Not the User or System Library.) On most Unix systems, a shared Cake install goes to \/usr\/lib.<\/p>\n
\nIt’s likely you want to work on your Cake application somewhere other than \/Library. And you probably don’t feel like modifying httpd.conf either. So good news – you can simply move the \/Library\/Cake\/app folder wherever you feel like working – and name it whatever you like. You can also duplicate this folder and create multiple<\/span> Cake apps. I simply put it in my home directory. Thus, I end up with \/Users\/myhomedir\/app. If I want to start a blog application (like the tutorial app<\/a>, for example) I’ll duplicate that folder and rename it ‘blog.’ I can duplicate this folder over and over to create my applications.<\/p>\n
\nNow that you have your library and applications folders in place, you need to move Cake’s webroot directory into the place where you want to serve your files from. For example, when you activate Personal Web Sharing, the Apache serves files from \/Library\/WebServer\/Documents. If I move \/Users\/myhomedir\/app\/webroot to \/Library\/WebServer\/Documents\/webroot, then my Cake application will be accessible at http:\/\/localhost\/webroot\/. If I copy the contents<\/span> of app\/webroot, to \/Library\/WebServer\/Documents, then my Cake app will simply serve out of http:\/\/localhost.<\/p>\n
\nNow all your files are in place. To give Cake a working install, though, you’ll need to tell it where your libraries and app files are!<\/p>\n
\nMy Cake Libraries are in \/Library\/Cake.
\nMy Application Folder is \/Users\/myhomedir\/blog.
\nMy Application Webroot is \/Users\/myhomedir\/Sites\/blog.<\/p>\n\/**\r\n* These defines should only be edited if you have cake installed in\r\n* a directory layout other than the way it is distributed.\r\n* Each define has a commented line of code that explains what you would change.\r\n*\r\n*\/\r\nif (!defined('ROOT')) {\r\n \/\/define('ROOT', 'FULL PATH TO DIRECTORY WHERE APP DIRECTORY IS\r\n \/\/LOCATED DO NOT ADD A TRAILING DIRECTORY SEPARATOR';\r\n \/\/You should also use the DS define to seperate your directories\r\n \/\/define('ROOT', dirname(dirname(dirname(__FILE__))));\r\n define('ROOT', DS . 'Users' . DS . 'myhomedir');\r\n}\r\nif (!defined('APP_DIR')) {\r\n \/\/define('APP_DIR', 'DIRECTORY NAME OF APPLICATION';\r\n \/\/define('APP_DIR', basename(dirname(dirname(__FILE__))));\r\n define('APP_DIR', 'blog');\r\n}\r\n\/**\r\n* This only needs to be changed if the cake installed libs are located\r\n* outside of the distributed directory structure.\r\n*\/\r\nif (!defined('CAKE_CORE_INCLUDE_PATH')) {\r\n \/\/define ('CAKE_CORE_INCLUDE_PATH', FULL PATH TO DIRECTORY WHERE\r\n \/\/CAKE CORE IS INSTALLED DO NOT ADD A TRAILING DIRECTORY SEPARATOR';\r\n \/\/You should also use the DS define to seperate your directories\r\n \/\/define('CAKE_CORE_INCLUDE_PATH', ROOT);\r\n define('CAKE_CORE_INCLUDE_PATH', DS . 'Library' . DS . 'Cake');\r\n}<\/pre>\n\r\nvar $default = array('driver' => 'mysql',\r\n 'connect' => 'mysql_connect',\r\n 'host' => 'localhost',\r\n 'login' => 'mymysqluser',\r\n 'password' => 'foxessuckoknotreally',\r\n 'database' => 'blog',\r\n 'prefix' => '');\r\n<\/pre>\n
\nStart coding!<\/p>\n