The LAMP stack is the foundation for Linux hosted websites is the Linux, Apache, MySQL and PHP (LAMP) software stack.
The Four Layers of a LAMP Stack
Linux based web servers consist of four software components. These components, arranged in layers supporting one another, make up the software stack. Websites and Web Applications run on top of this underlying stack. The common software components that make up a traditional LAMP stack are:
- Linux: The operating system (OS) makes up our first layer. Linux sets the foundation for the stack model. All other layers run on top of this layer.
- Apache: The second layer consists of web server software, typically Apache Web Server. This layer resides on top of the Linux layer. Web servers are responsible for translating from web browsers to their correct website.
- MySQL: Our third layer is where databases live. MySQL stores details that can be queried by scripting to construct a website. MySQL usually sits on top of the Linux layer alongside Apache/layer 2. In high end configurations, MySQL can be off loaded to a separate host server.
- PHP: Sitting on top of them all is our fourth and final layer. The scripting layer consists of PHP and/or other similar web programming languages. Websites and Web Applications run within this layer.
We can visualize the LAMP stack like so:
Applying what you’ve learned
Understanding the four software layers of a LAMP stack aids the troubleshooting process. It allows us to see how each layer relies on one another. For instance; when a disk drive gets full, which is a Linux layer issue. This will also affect all other layers in the model. This is because those other layers rest on top of the affected layer. Likewise, when the MySQL database goes offline. We can expect to see PHP related problems due to their relationship. When we know which layer is exhibiting problems. We know which configuration files to examine for solutions.
The four traditional layers of a LAMP stack consist of free and open-source products. Linux, Apache, MySQL and PHP are the cornerstone of a free, non-proprietary LAMP stack. There are several variants of the four stack model as well. These variants use alternative software replacing one or more of the traditional components. Some examples of these alternatives are:
- WAMP: Windows, Apache, MySQL & PHP
- WISA: Windows, IIS, SQL & ASP.net
- MAMP: MacOS, Apache, MySQL & PHP
You can explore these alternative software stacks in greater depth using online resource. The LAMP stack Wiki is a great place to start:
How can we help?
The LAMP stack is an industry standard and is included in all of our Core-Managed and Fully Managed Linux based servers. Our support teams work hand in hand with the LAMP stack on a daily basis. You can rest assured we are at your disposal should you have questions or concerns. To learn more you can browse our latest product offerings.
When working on a WordPress site, especially stores, you’ll likely reach a point where you need something custom. You might want to customize something that doesn’t have a true setting in WordPress? Or, you need to add a custom hook to modify something? Or, maybe you need to customize part of your WooCommerce store?
No matter the case, making code changes means you’ll need to know the right place to do that. In this article we cover the best ways to get this done and some best practices.
Continue reading “Managing code snippets in WooCommerce”
Behind Cloud Sites, racks full of both Linux and Windows servers power over 100,000 sites and applications. Every Windows-based page is served from clusters built and optimized especially for Windows, and every Linux-based page is served from clusters built and optimized especially for Linux. We use advanced load balancing technologies to automatically detect the type of technology you are running and route each request to the proper pool of servers.
This is a great example of the power of cloud computing, since you no longer have to make a hosting choice between Linux and Windows. Both PHP and .NET are included, allowing you to choose the technology you need site by site.
Continue reading “Choosing Your Cloud Sites Technology Setup”
Best Web Development Tools of 2017: Editors/IDEs and Package Management
The worlds of web hosting and web development are in a constant state of evolution. Every year we see design trends change, coding standards adapt and new frameworks/CMS created. With such a quick pace of change it’s easy to get lost trying to keep up.
As a web hosting company we don’t often talk about the tools used to create the web. We’re usually ultra focused on the components that enable us to server and support you; things like: server hardware, Linux, Apache and etc.
We may not support development tools, but we do want to help our customers to build amazing stuff.
Continue reading “Best Editor for Web Development 2017”
With the release of EasyApache 4 in WHM 58 there are various changes to how PHP is managed. The most obvious being that EasyApache 4 brings support for installing multiple PHP versions alongside each other. However with multiple versions of PHP being installed on the server it’s easy to lose track of your command-line based PHP utilities and their PHP requirements. Continue reading “EasyApache 4 & CLI based PHP utilities”
Depending on the site or application, looking up geographic information related to an IP address can be a pretty common action. When doing IP geolocation in PHP usually the PHP GeoIP extension would be used to facilitate the retrieval of this information. Unfortunately, this particular plugin is no longer actively supported and has not been updated in a number of years.
With the go-to PHP extension of IP geolocation effectively being deprecated, new projects should begin to use the replacement options that are now provided by MaxMind. However, unlike the original GeoIP, which was shipped as a native PHP extension, the new solutions are provided as PHP-based library packages. Continue reading “How to Replace PHP GeoIP with MaxMindDB”
In the previous articles we worked through what composer is, who uses it, and how to install it. Here we will cover some basic use case examples of how to acquire packages using the composer tool we previously setup.
The example documented in this article can be done either locally, or on your Liquid Web Fully Managed cPanel server, in either case these directions should be run as the user owning the website files. On a cPanel server this would mean you’re running these via SSH logged in as the cPanel user and you would be starting from within public_html. Continue reading “Working with Composer & Examples”
With a tool like Composer it is generally best to have the ability to run it as any user on the server and from any directory. This is generally referred to as being ‘globally installed’ as any user can access the tool from any location. In this guide we will detail how to install Composer globally on a cPanel based server. Continue reading “Installing Composer on cPanel servers”
Composer is a dependency manager for PHP, written in PHP. Specifically, it’s used to simplify the process of using PHP libraries in your projects. The use can range from getting a framework, including a library class, or open source projects; generally these packages are downloaded by Composer and then implemented by a developer in a website’s code. Continue reading “Composer 101”
Your fully managed cPanel server has several different PHP handlers from which to choose, including DSO, SuPHP, and FCGI. These handlers are responsible for reading/interpreting PHP code, then compiling and executing it.
Selecting the best PHP handler for your server is critical to overall performance, but it’s not always an easy choice to make. While FCGI currently is the best-performing PHP handler available on cPanel, it can be somewhat difficult to properly configure.
Since we’re the best Managed Hosting company around, we decided to take care of the initial configuration for you to help make your decision that much easier.
Liquid Web has spent the past few months optimizing FCGI settings to achieve the best performance gains possible while lowering resource utilization and further improving stability. Today, we’re thrilled to announce that we’ve updated our Fully Managed CentOS 6 and CentOS 7 templates to include these optimizations by default!
What type of performance gain does FCGI provide over SuPHP? We’re glad you asked!
To measure performance, we installed a default WordPress site on a Zone C 16 GB Storm VPS, then used Apache Benchmark to hit the server with 10 concurrent connections, and a total of 1,000 requests.
With SuPHP as the PHP handler, we were able to get around 30 requests per second. Once we switched the PHP handler to FCGI with our optimizations (which include enabling and configuring OPcache), we were able to get more than 150 requests per second! In this case we saw a 500% increase in performance!
These optimizations are not reserved for new Storm® VPS and Dedicated servers, either. If you have an existing fully managed cPanel server and would like to take advantage of the performance gains FCGI and OPcache can bring to your sites, let us know! Our Heroic Support® technicians can quickly examine your server’s current settings and walk you through any changes necessary to help your server realize its full potential with FCGI and OPcache.