On the "Learn Computer" site there's a recent post that wonders if the web development standard of the LAMP (Linux, Apache, MySQL and PHP) stack is "still strong" and will still stand up with new technologies.

This year in tech (like almost every other year) has been filled with buzzwords. Many of them this year, however, are based around big data processing and web content: NoSQL, Hadoop, BigTable - the list goes on. With all the fuss around these new technologies, one might be tempted into thinking that these are the technologies of the future, and that from now on our servers and websites will be built upon, leaving technologies like LAMP in the dust.

They talk about some of the things the LAMP stack doesn't do well like difficulties with scalability on both the web server and database side. There's also mention of the things that it does do well, like getting things up and running quickly and with a solid structure.

That being the case, the LAMP stack is still going very strong, and it's definitely still extremely viable in small and medium-sized deployments; there are no signs of it waning in that regard, and I'd expect it to be a standard deployment for many companies and organizations for quite some time to come.

Tecmint.com has a new tutorial that walks you through the installation of a full LAMP stack (Linux, Apache, MySQL and PHP) on a CentOS or RedHat installation.

This howto guide explains you'll how to install Apache Server with latest MySQL 5.5.27 and PHP 5.4.7 versions with php required following modules on RHEL 6.3/6.2/6.1/6.0/5.8/5.6, CentOS 6.3/6.2/6.1/6.0/5.8/5.6 and Fedora 12,13,14,15,16,17 systems using Remi repository via Yum tool.

Thankfully, package management has made things a lot simpler than they used to be. Most of the time you're only a few commands away from a working installation (if all you need are the generic setups). They explain what each piece of the installation is and how to set up the custom "Remi" yum repository to get the latest versions of the software - Including PHP 5.4. They show how to stop and start each of the servers (MySQL, Apache) and a few screenshots of what the output of your phpinfo page should look like.

In this recent post to Reddit.com, a "solid novice with PHP" asks the community for some insight into what the day-to-day life is like for an average LAMP developer.

I wanted to hear from someone who does LAMP development for a living, What does your work day look like? That is to say that, I have no idea what the responsibilities for a LAMP developer look like. Are these people putting together entire websites on various platforms (wordpress, joomla, whatever)? Are you simply doing backend work (setting up databases, working with tables, etc)? All of the above?

The comments on the post talk about things like:

• The differences between the "startup" and "business" life of a typical developer
• Sympathy over some of the debugging methods in PHP
• Technical issues
• Working as a lone developer
• The variety of skills needed
• Discussion of specs and system architecture

What's your average day like? Share it here!

In this recent post to the Nodeable Blog, they suggest that the days of the typical LAMP stack (Linux, Apache, MySQL, PHP) are numbered because of what many of the cloud services have to offer.

For the past 10 years, the LAMP stack has laid waste to proprietary software stacks. Yes, Microsoft has held onto gargantuan profits, but LAMP has become the foundation for leading web services, whether Google or Facebook or [Insert Big Web Brand Here]. LAMP is the future. Or was. That is, until cloud killed it, as Eucalyptus CEO (and former MySQL CEO) Marten Mickos posits in a great keynote from the Percona Live: MySQL Conference & Expo 2012.

In the keynote he pointed out that it's becoming less about the whole setup and more about combining technologies to get the results you need - less "stack" and more "linked technology" (and not always the same tech for every node). He pointed to the Amazon AWS service as a prime example of a platform that allows endless flexibility as to what software can be installed and how it can be used, all with a few clicks of a mouse.

In this tutorial on the XPertDeveloper site today they show you the "quick and not-so-dirty" way to get PHP + Apache + MySQL set up on a Ubuntu machine (from packages).

I have started working with Ubuntu 11.10 and my first task was to install PHP, Apache and MySQL in that. This is because without these three things computer is useless for PHP Developer. So Here I am sharing this article which shows how to install PHP, MySQL and Apache and configure with each other. This would be very useful for newbies, who have just jumped into web developing.

The process mostly consists of installing a few packages - mysql-server, mysql-client, apache2, php5 libapache2-mod-php5 (as well as several others for various PHP extension support) - and starting up the default Apache server.

In this new post to his blog Brian Swan shares the process that he and other Microsoft-ers went through to migrate a site off of a LAMP stack and over to one based on Windows Azure. They moved was the SAG awards website because of issues it had seen with outages and slow performance.

In many ways, the SAG Awards website was a perfect candidate for Windows Azure. The website has moderate traffic throughout most of the year, but has a sustained traffic spike shortly before, during, and after the awards show in January. [...] The main challenge that SAG Awards and Microsoft engineers faced in moving the SAG Awards website to Windows Azure was in architecting for a very high, sustained traffic spike while accommodating the need of SAG Awards administrators to frequently update media files during the awards show. Both intelligent use of Windows Azure Blob Storage and a custom module for invalidating cached pages when content was updated were key to delivering a positive user experience.

He walks you through each of the five steps (high-level, obviously) that they took in the migration:

• Export data
• Install Drupal on Windows
• Import data into SQL Azure
• Copy media files to Azure Blob Storage
• Package and Deploy Durpal

Each step comes with some explanation and descriptions of the commands and tools used during the process.

In this new article on DZone.com, Artur Mkrtchyan shows you how to get an Amazon EC2 instance up and running and get a LAMP server set up and ready to go.

In this article I'm going to show you how to create a free Amazon EC2 cloud based LAMP Server and Point your domain to Amazon EC2 Instance. There are 4 simple steps to do.

The setup process is pretty easy - getting an Amazon free account, creating a server from an existing image, installing the LAMP stack and pointing your domain at the EC2 instance. He gives a step-by-step guide of the process, including the commands you'll need to execute to get all of the LAMP packages installed.

These days there's much more involved in making a good, solid web application than just the platform you serve from. Joshua Thijssen knows this and humorously points it out in a new post about a "LAMPGMVNMCSTRAH-stack" (that's fifteen different technologies for those counting).

Back in the good old days - and in internet-time, this actually means just a few years ago - people were quite happy with their LAMP stack: Linux, Apache, MySQL and PHP. With this quartet, or a variation on it like PostgreSQL instead of MySQL, we could do everything: create a blog-site, setup an e-commerce web shop, making a guestbook, you name it and it was there.. But times have changed... radically.

He talks about this "brave new world" developers live in today where they can't know everything that happens in every facet of the application (he likens it to the responsibilities of generals vs infantry in the army).

As a programmer, you simply cannot pretend that you and you alone are running a system. You are part of a whole, and even though you might be the most important part, or the controlling part, you still need to work with other components in order to get the job done. If you forget this, no matter how good your part is running, the whole system will fail because you either decided to do too much yourself, or did not correctly utilize the rest of the system.

Wondering what his acronym stands for? LAMPGMVNMCSTRAH is short for "Linux, Apache, MySQL, PHP, Gearman, Memcached, Varnish, Ngnix, MongoDB, CouchDB, Solr, Tika, Redit, ActiveMQ, Hadoop."

If you're a user of Ubuntu 11.04 (Natty Narwhal) and are needing to get a full LAMP stack up and running, you're in luck. Omar Abdallah has put together a guide to help with just that.

I wont cover what's new in php 5.3 since it would be another article, however it contains alot of improvements including PHP Namespaces, Late Static Bindings, lambda functions, closures...etc. I would strongly recommend using it. I'll be explaining how to install LAMP stack with PHP 5.3.6 without compiling. It's fairly easy using the dotdeb repository.

He steps you through adding the dotdeb package locations to your plist file and pulling down the GPG key for the connection. The rest is a simple "aptitude install" command away, pulling in the apache2, mysql, php5, mcrypt, curl, gd and phpmyadmin packages.

In a recent post to his blog Wojciech Sznapka shows you how to set up your local development environment so that you're not having to configure a VirtualHost (assuming you're using Apache, of course) each time you want to work on a new project.

If you are developing PHP application on your own PC, you probably have some vhost based configuration of your Apache. With some tricks, you can turn your Linux box into powerful development server without configuring vhost for every app. [..] We can ommit two lasts steps [of a typical setup process], limiting preparation of the environment only to place source code somewhere in filesystem. To achieve this we need mod_vhost_alias module for Apache2 and simple DNS server which will resolve local domain names for us.

His tip uses the mod_vhost_alias module for Apache and the dnsmasq tool to make the basic DNS server to resolve these custom domains. A few configuration changes later (included) and you're set to restart apache and be on your way.