|
 |
|
|
LAMP4U-Linux et al for the World
LAMP-the acronym sweeping the Internet stands for Linux-Apache-Mysql-Perl, Python or Php Here is an explanation from a website dedicated to LAMP http://www.onlamp.com/pub/a/onlamp/2001/01/25/lamp.html an excerpt from the above article is worth considering: "The lightbulb that went off in my head was that LAMP represents the open source web platform. Most importantly, LAMP is the platform of choice for the development and deployment of high performance web applications. It is solid and reliable, and if Apache is any indicator, then LAMP sites predominate. If you visit the Netcraft survey and look up popular sites, you'll notice that many run Apache on Linux, and have either mod_perl or mod_php installed. (Netcraft is unable, using its methodology, to detect sites that use MySQL, but we feel comfortable, knowing the number of MySQL downloads, that this open source database is making significant inroads on proprietary databases, especially for web applications.) There was one more ah-hah factor with LAMP. I realized that we used LAMP at O'Reilly Network. Our customized content management system, Community Server, is a LAMP platform, consisting of Linux+Apache+MySQL+Perl. Another important project at O'Reilly Network is Meerkat, an RSS syndication server, and it uses Linux+Apache+MySQL+PHP. So we not only believe in LAMP; our Web sites are built on LAMP. It also happens that our strongest affiliates on the O'Reilly Network are LAMP-related: Apacheweek.com, MySQL.com and Perl.com. In addition, we have developed a sizeable amount of content on O'Reilly Network for Apache, MySQL, PHP and Python developers." with the above introduction, the authors set up a site dedicated to the concept of LAMP. and a short article that Tim O'Reilly posted is well worth considering as well, here is the URL, and then the article: http://www.onlamp.com/pub/wlg/3037
"The following email from Bill Good (bgood AT inceptual.com) was so thoughtful that I asked Bill if I could repost it. Like Bill, I loved Zen and the Art of Motorcycle Maintenance, and it was great to see this seminal book brought up in the context of open source. Here's Bill's message (with links added by me):
While this may be out somewhere in left field, I would suggest that another way to express the success of Open Source communities is its embodiment of an idea I first encountered in Robert Pirsig's Zen and the Art of Motorcycle Maintenance. In chapter fourteen, Pirsig recounts a conversation with Robert DeWeese, an acquaintance with whom Robert and his son are staying. The conversation revolves around a set of instructions for assembling an outdoor rotisserie grill. While Pirsig thinks about the technical correctness of the instructions and DeWeese expresses frustration with the "lack of artistic continuity," Pirsig's son Chris refolds the instructions so that an illustration sits next to its text. This seems to maintain the accuracy of the instructions while providing a style which is easier to follow. The beauty of Open Source-centric communities is that refolding the instructions is not only allowed, but encouraged. Refolding Mozilla has produced several applications, each of which uses the Mozilla framework while satisfying another end. Indeed, Mozilla.org even lists several projects not associated with the Mozilla project itself but which use the Mozilla framework itself. (And, let's not forget the O'Reilly book, Creating Application with Mozilla, by David Boswell et al.) Pirsig's conversation and thought process goes on and there are several gems to be found. One that still sticks with me even today is: "What's really angering about instructions of this sort is that they imply there's only one way to put this rotisserie together -- their way. And that presumption wipes out all the creativity. Actually, there are hundreds of ways to put the rotisserie together and when they make you follow just one way without showing you the overall problem, the instructions become hard to follow in such a way as not to make mistakes. You lose the feeling for the work. And not only that, it's very unlikely that they've told you the best way." Having gone through my first couple of OpenBSD installations, I know exactly what Pirsig must have felt. In a previous lifetime, I worked with proprietary systems, a la Armonk, New York, and Redmond, Washington. The instructions I had offered one way to install the software. If I didn't grasp the instructions or the prescribed solution, then I looked elsewhere. But, elsewhere I only found rehashes of the official procedures or solution. As mentioned in your conversation with Adam Turoff and in Matthew Langham's post, such conditions were the result of the software's originators and the subsequent communities. One could say that the instructions were merely photocopied and redistributed, rather than refolded into a new orientation. When I recently installed OpenBSD and its implementation of SendMail and BIND, I again came to a point where the developers' instructions stumped me. Unlike before with proprietary software, I found the instructions for Open Source Software presented in many different formats and from many different perspectives. Taking a bit here and a bit there, I was able to assemble enough information to build mail and DNS systems that worked for my situation. Not only had the community "refolded" the instructions, some members had chosen to escape paper and use sculpture, watercolor, song, and dance, so to speak. More importantly, I felt the solution I had crafted for my installation would be just as acceptable to the community as that directed by "official" documentation. In other words, I don't expect a reply in any forum to read "That workaround is not supported," which is exactly what I would have received in many proprietary software's support forums. In other words, my solution is one of "hundreds of ways to put the rotisserie together" and the grill makers (a.k.a. OpenBSD, SendMail, and BIND) haven't made any presumptions which stifle the creativity around implementations. In short, one might find that the points recently made about OSS answer some interesting questions raised in a forty year old philosophy book." Tim O'Reilly is founder and CEO of O'Reilly & Associates and an activist for Internet standards and for open source software. LAMP HOW TO: Apache & Python How To: http://www.onlamp.com/pub/a/apache/2003/04/10/apacheandpython.html a how to article is posted at: http://www.mkaz.com/reference/php/setup_linux.html LAMP URLs: http://www.toppoint.de/~tulli/lamp.html
|
