LAMP Stack Debian 13

I have been using LAMP Stack Debian for more than six years. My main use case involves developing PHP web applications, utilizing PHP, MariaDB, and Apache. I developed a couple of applications including a book sharing application where users can share their books with other users of the same site, and an application around an HR system where the HR admin of a particular company can manage employees, their appraisals, interviews, and job offers. I mostly develop PHP applications using LAMP Stack Debian, and there were many applications I developed for personal use as well as for company projects, generally developed in core PHP.

The best features that LAMP Stack Debian offers include easy installation on both local machines and servers, which I have found to be very straightforward. I have not faced any issues using LAMP Stack Debian. I can start it anytime using the terminal and stop all three services in one command. It is very useful to easily modify configuration files like php.ini, the Apache configuration file, and .htaccess. Accessing SQL using MariaDB or MySQL is also very easy and straightforward, making development very fast.

The feature I appreciate the most in my daily work with LAMP Stack Debian is the easy setup. I find this most useful whenever I change my laptops, as I can quickly set up LAMP Stack Debian without any issues.

LAMP Stack Debian positively impacts our organization by making our development process easy for PHP applications, providing many features, and improving our productivity. It is easy to install without facing installation issues, as we do not struggle with installing PHP, Apache, and SQL database separately; all three are part of the same installation process. This is a useful feature that makes our development and daily tasks easier. I have noticed faster project delivery times due to using LAMP Stack Debian, along with less time spent on setup, resulting in a quick turnaround for development.

I believe LAMP Stack Debian is mostly comprehensive, but it could be improved by making the installation UI-based, similar to Windows, where users can just click next, next, next, allowing fresh users to quickly install it without hesitation. Experienced users will still find the existing process easy, but novice users who do not have terminal access can benefit from a more guided installation.

I have been working in my current field for around 17 years.

LAMP Stack Debian is definitely stable.

The scalability of LAMP Stack Debian is good.

Customer support for LAMP Stack Debian is also good, as it has been around for a long time. I would rate the customer support of LAMP Stack Debian a nine on a scale of one to ten.

I have been using LAMP Stack Debian since the beginning, so I did not previously use a different solution.

LAMP Stack Debian is very straightforward to install and requires minimal effort for setup, making the process seamless.

There is no need for a separate IT person to set up LAMP Stack Debian, as a developer can manage it themselves.

I have definitely seen a return on investment with LAMP Stack Debian, as it saves time and money, and also requires fewer employees since we do not need a separate IT person to set it up on machines; a developer can manage it themselves. This is what I call a return on investment.

I find the pricing, setup cost, and licensing for LAMP Stack Debian to be reasonable.

Before choosing LAMP Stack Debian, I evaluated other options that involved installing PHP, Apache, and MySQL separately, but I opted for LAMP Stack Debian because that setup would take much more time.

I do not have any specific advice for others looking into using LAMP Stack Debian; I can just say that it is awesome. If you are choosing any PHP installation, then use LAMP Stack Debian. I would rate this product a nine on a scale of one to ten.

I have been using LAMP Stack Debian for approximately ten years. I use LAMP Stack Debian for projects that require PHP with a connection to MySQL. Additionally, I use LAMP Stack Debian when I need to deploy websites such as WordPress, PrestaShop, or projects that are already running on PHP and MySQL or MariaDB.

The website of my company and the website of my product run on WordPress and are hosted in an Azure container, where Debian is installed with LAMP. At the domestic level, I set up my personal website when I used WordPress; although I currently use Grav, I previously used LAMP. Since Debian is an extremely stable distribution, it seems to me to be a very sound solution.

I decided to migrate and standardize my production environment to Debian seeking predictability. The benefit is significant because it has resulted in a drastic reduction in downtime and maintenance costs, knowing that a routine security update will not break anything and that the PHP runtime environments and Apache configuration provide me with enormous peace of mind in my daily work. I use LAMP Stack Debian in a public cloud that runs on Azure Cloud.

What I highlight most about LAMP Stack Debian is the absolute stability and consistency of the environment. When managing standard websites such as WordPress or PrestaShop, up to critical enterprise applications in production, I need an underlying operating system that does not introduce abrupt changes. Debian offers exactly that.

The integration of the traditional LAMP architecture, Linux, Apache, MySQL, MariaDB, and PHP, in Debian is impeccable. The APT package management system handles dependencies cleanly, and Debian's security patch policy ensures that the server remains protected without breaking compatibility with existing applications. Additionally, the resource consumption of this stack on Debian is extremely optimized compared to other distributions.

The minimalism in the base installation of Debian, with no bloatware, is outstanding. I install directly with APT; I install .deb packages, which means that Apache, PHP, MariaDB, or MySQL communicate directly. There is no abstraction layer between them, eliminating all translation layers and reducing latency. Another aspect I appreciate about Debian is the restrictive policies for background services in systemd, which keeps these services to a minimum and mitigates unjustified spikes, leaving computing power available to process PHP code.

One of its virtues is also one of its problems. The main drawback is the old age of the packages; in the stable branch, I do not get the latest versions of PHP, Apache, or similar software. Therefore, if I want something, I have to go to trusted external repositories or compile something manually to be on the cutting edge. That is the only downside I see.

I have been working in my current field for twelve years.

LAMP Stack Debian is exceptionally stable.

I have had to scale up or down resources at various points. I have vertical and horizontal scaling available at the Azure layer, which is straightforward to apply, and on Debian, it is applied almost automatically, requiring only a few commands. The fine-tuning of LAMP is quite simple.

I have not used official support so far. I have always turned to the community. There is a large community in Debian where I can find solutions to any problem because it has probably happened to someone else before. The community is excellent, and I do not have any concerns regarding support.

I have used Debian, Ubuntu, CentOS, and many other solutions, but I moved to Debian precisely because of the support, long-term support, stability of the packages, and community maintenance.

The installation process is quite simple because, with the APT tool, it is easy to install LAMP. It is true that the default configuration that comes out of the box is somewhat sparse, and I have to do some manual tuning by editing clean configuration files, but it is nothing complicated if I have handled PHP, MySQL, or Apache before.

The Debian Wiki is my central reference. I do not need to go to any blog because it has a lot of reliable documentation, and I also find the right documentation for the distribution I am using. This documentation could be improved because the Wiki looks outdated, but it is very good. The system manuals and man pages are perfect because they are included with everything. If there are still things missing, the ecosystem and the global community are excellent. There is a large community where, if I have any problem, I will find a solution quickly and accurately.

There have been time savings in terms of configuration. There have been time savings in terms of vulnerabilities or fixes, and there has also been a return on investment in terms of resources since I do not need large resources for the projects I have.

It has drastically reduced reactive maintenance. In my department, infrastructure updates usually generate friction because we are afraid that something will break. The impact it has had is that LAMP Stack Debian stable's policy, by not introducing major version changes in security packages, has transformed maintenance from something stressful into something predictable. The infrastructure team no longer spends the weekend stressed out, fixing incompatibilities or worrying that nothing critical would come up in the next few hours. The return on investment is significant; since hardware and cloud efficiency is quite high, I need less hardware to handle more traffic. With a much smaller machine in Azure, I can deploy many more sites than before, when I had to oversize with other solutions. In the end, there is also the guarantee of business continuity; I know that Debian distributions have great long-term support, so I am confident that I have guarantees for business continuity for quite a long time. The savings come from the fact that since the machine is very optimized, I need fewer machine resources to launch the same sites, and therefore I run more solutions on smaller machines. This translates into lower cloud costs. Regarding business continuity, the fact that updates or distributions have long-term support implies that the distribution will remain supported for much longer.

LAMP Stack Debian has no license cost. By choosing a free solution, 100% Apache 2.0 licensed, I do not have any concerns of any kind.

I evaluated Ubuntu, but Ubuntu's LTS versions are shorter than those of Debian. That was the main reason why I chose Debian.

I use LAMP Stack Debian as a central infrastructure to deploy and host internal developments and commercial e-commerce or CMS platforms.

LAMP Stack Debian is a very good choice for stable projects that have little variability, especially for websites made in WordPress, PrestaShop, and projects that require high stability. I rate this solution an 8 out of 10.

My main use case for LAMP Stack Debian is for web application development and reverse proxy engineering, where I apply security ACLs for infrastructure in my campus and at other companies where I have worked. Most of my cases involve web applications that are self-hosted based.

A quick specific example of a web application I have hosted or managed with LAMP Stack Debian is hosting the website of the company and hosting web applications such as tools and ERPs for the company, which are based mostly on Apache and MySQL databases, primarily MariaDB databases, exclusively based on LAMP architecture.

LAMP Stack Debian has impacted my organization positively through stability. Apache does not change that much, which is good because when you are trying to patch your whole infrastructure, you might sometimes face cases where your configuration no longer works because you have upgraded the web server. With Apache, which is quite stable, you do not encounter many cases that cause problems. It can happen that one of the modules changes, but it remains compatible. Retro-compatibility is one of the main advantages with Apache.

When I mention retro-compatibility and stability, it has saved me time and reduced downtime significantly. It makes life much easier when you are upgrading new systems. For instance, whether you are going from an old Debian 10 to 11 or 12, there is not a big change regarding Apache because Apache remains retro-compatible with the other operating system. This is one of the main points. You are definitely reducing the risk of having downtime.

The best features that LAMP Stack Debian offers in my experience include scalability concerning databases. Most of the features that you can do on Apache involve the web interface where you are listening on port 80, but you can also add features in terms of security where you can tweak and add proxies, new ACLs, and get other tools like WebDAV, which stands out compared to other web servers such as Nginx, which is the main competitor of Apache.

These features, specifically WebDAV, have helped me in my day-to-day work because I have used WebDAV when some customers needed to have access to our files but could not use SFTP, NFS shares, or other classical ways to share a large amount of data. WebDAV stood out as the main solution and the perfect fit because anyone nowadays has a web browser, either on a computer, a smartphone, or other devices. This solution was the one we approached and it proved to be the ideal solution.

LAMP Stack Debian can be improved by providing an out-of-the-box cluster solution without having to build it around it. A cluster solution would make life easier for everyone.

Regarding LAMP Stack Debian's governance and security, this is still something that needs to be experienced, as it is too soon to jump into a conclusion.

Regarding LAMP Stack Debian's accuracy and reliability of output, this is very accurate from what I have tested.

There are no other improvements needed for LAMP Stack Debian that I have not mentioned.

I have been using LAMP Stack Debian for approximately 14 years.

LAMP Stack Debian is stable.

LAMP Stack Debian's scalability is very high.

My experience with LAMP Stack Debian's scalability includes having to scale up or down quickly or manage a large number of users or applications through an HAProxy to failover between two stacks.

I previously used Nginx instead of Apache, mostly because I was using an HAProxy solution.

My experience with pricing, setup cost, and licensing for LAMP Stack Debian is great.

I have seen a return on investment, knowing that most of the tools around LAMP are free. You cannot have a negative outcome. You can only have a return on investment.

My experience with pricing, setup cost, and licensing for LAMP Stack Debian is great.

The advice I would give to others looking into using LAMP Stack Debian is to understand the size of the need that they require. They need to understand and size up the requirement accordingly. The review rating for this product is not available.

LAMP Stack Debian is basically a full backend, very often used for WordPress hosting, which is my primary use case.

One of the things that I have been working on is setting up an automated pipeline for a customer to deploy WordPress, and I needed to deploy LAMP Stack Debian with those instances as well. We ran this in Kubernetes, for example.

If you ever want to ask a beginner Linux administrator to set up a web server, they are probably going to set up LAMP Stack Debian to showcase that everything is working. It is the default for a lot of web hosting, and I think it has very mature tooling and a really strong integration into Linux.

The internet runs on Linux, and websites will run on LAMP Stack Debian, which is very easy to deploy. If you want to set up a web server, you can do that with LAMP Stack Debian within a few minutes.

LAMP Stack Debian is very often deployed in some kind of cloud environment, also used a lot on VPSs and in Kubernetes. It runs well in containers as well, and it runs on bare metal; you have a couple of options there.

I think that LAMP Stack Debian is not necessarily a very good stack, but it is a very proven stack, and that is where it really shines. It is an industry standard.

It is also interesting to call out that LAMP Stack Debian comes in two flavors; the default is of course MySQL, but you can also use MariaDB, whatever you prefer. This is also a little bit operating system dependent.

I have nothing measurable to share, but a lot of stacks are based on LAMP Stack Debian as a backend or as a web server, and LAMP Stack Debian is extremely reliable and extremely proven. It is something you do not have to discover yourself; you just take LAMP Stack Debian and it works.

It is an old stack, and I am not necessarily a fan of PHP, to be honest. This is not improving LAMP Stack Debian but changing it. I am not necessarily a fan of PHP, but it is very performant and it uses very little resources. I also like using other stacks as well. How can it be improved? LAMP Stack Debian itself, I do not think can be improved; it is continuously updated with MySQL and with the proxy that is in there, the MySQL database that is in there, and the PHP server. I do not think it can be improved; there are other more contemporary stacks that might be interesting to consider, but LAMP Stack Debian is always updated. Things the .htaccess file can sometimes be a bit finicky with the Apache proxy.

I think that will become then a different stack, and the Apache HTTP server is not a proxy. It is what it is; it is very much proven. If you change that, then it is not proven anymore.

I have been using LAMP Stack Debian on and off for the past ten years.

LAMP Stack Debian is very stable.

Its scalability is good, if not excellent; if you have very large websites, it might not work, but I would say for ninety-nine percent of the use cases, for WordPress, a simple LAMP Stack Debian will absolutely do. You can, of course, scale your database into a bigger system, but if you are going to go down that route, you are going to use a different kind of website altogether.

It is open source. You go to Stack Overflow or whatever and find your solution. There is also managed LAMP Stack Debian where you get better support, but in essence, I would argue there is no support because it is open-source software; everybody can use it.

I would not argue that I was using a different stack before that; different use cases have different stacks, and for a specific use case, you use LAMP Stack Debian.

I would advise others to just give LAMP Stack Debian a try; try it on your Raspberry Pi or your local computer so you get your bearings. Know that there are Helm charts out there for Kubernetes so you do not have to write them yourself; it is a great way of getting started.

There is no cost associated with it, so there is no pricing, no licensing, and thus, there is no return on investment.

LAMP Stack Debian is open-source software, so I do not purchase it at all.

I did not evaluate other options because LAMP Stack Debian is defined by whatever tool you are trying to install, so that is more of a given.

I do not think it is the best stack out there; I think there are better stacks out there, but it depends on your use case, and it is boring but proven and good. You cannot go wrong with choosing LAMP Stack Debian, but in the end, I think there are better alternatives out there under development at least.

There are not any AI capabilities in LAMP Stack Debian.

There is no AI capability inside of LAMP Stack Debian.

I gave this product a review rating of seven.