this new blog setup took me 3 days of work, 12 opensource blog engines, 5 free hosting sites and many hours of frustration.
To reduce the frustration, I pointed him towards XAMPP. It has re-affirmed my belief (along with The Portable Suite and TiddlyWiki) that good things come in little sizes too. From its site:
Apache HTTPD 2.2.0, MySQL 5.0.18, PHP 5.1.1 + 4.4.1 pl1 + PEAR + Switch, MiniPerl 5.8.7, mod_ssl 2.0.55, Openssl 0.9.8a, PHPMyAdmin 2.7.0 pl1, XAMPP Control Panel 2.1, eAccelerator 0.9.4, Webalizer 2.01-10, Mercury Mail Transport System fÃƒÂ¼r Win32 und NetWare Systems v4.01a, FileZilla FTP Server 0.9.10a, SQLite 2.8.15, ADODB 4.65, Zend Optimizer 2.5.10a, XAMPP Security. For Windows 98, 2000, XP.
The least file size available is a self-extracting archive at 26MB, and a ZIP at 77MB. Now lets see, I got a pretty impressive setup on my machine – Apache 2.0.54 (4.66MB), PHP 4.4.0 (6.64MB), MySQL 4.1.13 (15.4MB), PHPMyAdmin 2.7.0 (1.87MB) and ActivePerl 5.8.7 (12.7MB). And the file size in toto? 41.27MB. And I don’t have an FTP or mail server or the other add-ons that they have listed… WOW!
Forget file size – XAMPP gives the user one control panel to configure its services and one directory to look after. Compared to what a user would have faced if he had installed the components individually, its utopia.
Compared with WOS Portable, XAMPP has a clear advantage in its array of components on offer; but as I’ve mentioned earlier, XAMPP is not truly portable, even if it is offered in an “unzip, run, delete” format.
And why am I not using XAMMP? Even after recommending it to others? Because where I’m headed, XAMPP is redundant. The environment would be just as I have set it up right now – independent directories and config files, etc. etc. But its nice to know that if I ever get frustrated with the LAMP/WAMP architecture, I can turn to XAMPP 😉 .