Linux for server configurations

Started by land_driver, Jun 28, 2022, 06:15 AM

Previous topic - Next topic

land_driverTopic starter

What Linux distribution do you recommend for a server?

While there are many different Linux distributions to choose from, I believe that Ubuntu Server is the best option for a server. Ubuntu is a stable and reliable distribution that is easy to set up and maintain.
It also has a wide range of applications and tools that can be used to customize the server to your specific needs. What Linux distribution do you think is best for server configuration?


I would not suggest UBUNTU .. Ease of use and setup is not something that should be considered a feature in servers and they're all actually about the same to setup.
ALMA LINUX is the way to go. It is not bloated, very fast, same support and it doesn't have the sketchy board and developers behind it like ubuntu / canonical. Think of zeitgeist , do you want to deal with the people who put this garbage in their software.


It doesn't really matter all that much these days, all the front runners are mostly stable, well rounded linux distros.

I personally have always used CentOS, starting at 6, then 7, then 8 and now AlmaLinux and never had problems that I haven't caused my self. however I have used Debian, Ubuntu and pretty much all others, and can happily switch between them without issue.


If we talk about the most popular distributions that are trusted by users, then among them I want to mention Linux Mint and Elementary OS. For macOS users, Elementary OS is the best distribution because its operating system closely resembles the interface of a MacBook.


CentOS. One of the most effective Linux distributions for the server, CentOS is used by almost 30% of all Linux servers in the world . Inherited from Red Hat Enterprise Linux, guarantees stable server health. The CentOS distribution has great functionality..

Jacques Chapman

I'm all for Ubuntu - to deny the stability and versatility, which with version 16.10 has become many times better, is stupid, but let's look at the rest.
For data centers, I would also consider the RHEL option. RHEL, aka Red Hat Enterprise Linux stands out for its large database scalability - it can withstand high speeds with 500 TB of databases.
Let's not forget about Linux Mint, which, apart from its functionality, is damn attractive and sеxy! In short, the functionality and appearance are somewhat reminiscent of Windows 7 (It's easier for people to switch to it).
I also want to remind you about the Debian distribution. Of course, it is difficult to learn and is intended for advanced users, but if you master it, then you will have a very extensive set of tools in front of you.


Standard Web Server configuration
The Apache Linux configuration for all virtual servers in the system is determined using the file /etc/httpd/conf/httpd.conf (in Red Hat Enterprise Linux, CentOS and CloudLinux) or /etc/apache2/apache2.conf (in Debian and Ubuntu).
The configuration files of virtual web servers are located at the lowest level of the configuration file hierarchy. They get into the Apache configuration file (last_httpd.conf) through several levels of inclusion using the include directive. nginx uses a similar approach: the /etc/nginx/nginx.conf file contains configuration files of all virtual servers through several levels of inclusion. Read about the Apache and nginx configuration file hierarchy.

Each virtual server in the system has two files – last_httpd.conf and last_nginx.conf – which define the standard Apache and nginx configuration for the corresponding virtual server. These files are located in the /var/www/vhosts/system/<domain name>/conf/ folder and are created automatically based on so-called configuration templates. Therefore, if you want to change the standard configuration of the server, you will need to make changes to these templates. How to do that, read the section Changing Virtual Hosts Settings Using Configuration Templates in the extended Administrator's Guide.

Individual configuration of the server
Some site owners may require additional server features that are not available in the standard configuration. For instance, support for special types of start pages or restricting access to the site by IP address. For such cases, Plesk has the ability to override the standard configuration for individual clients.

The standard server configuration can be redefined at the following levels:
The configuration specified at the level of the tariff plan replaces the standard configuration. In the properties of individual tariff plans, you can set any Apache and nginx directives. These settings are stored in the Plesk database and will be used by default for all customer sites (subscribers of the plan). See the section Web Server (Apache).

Website (virtual server)
The individual configuration at the virtual server (website) level replaces the configuration defined in the tariff plan. The Apache and nginx directives you set for a particular site are saved in the files vhost.conf, vhost_ssl.conf and vhost_nginx.conf (in the folder /var/www/vhosts/system/<domain name>/conf/).

There are two ways to configure the web server settings for a specific site:

Through the client panel interface. When you save your changes, Plesk will automatically create the appropriate directives in the appropriate configuration files. For details, see Changing Apache settings for Virtual web Servers and Changing nginx settings for Virtual Servers.

By manually editing configuration files. For detailed instructions, see the Extended Administrator's Guide, Virtual Host Configuration Files section.
Note: Only Linux root users can manually add and edit Apache and nginx configuration files.