With the correct packages we can quickly setup a simple CentOS 7 server to run a full LAMP stack.
This will turn our Linux system into a web server capable of serving out dynamic content from a database back end.
How can we find where the default configuration files for the httpd package in CentOS are located?
By using the RPM command we can query a package to find all of its associated configuration files. Failing that we can use the find command to search the file system for these files, as we will see here.
This WordPress based website loads fairly quickly, or at least I’d like to think so based on my testing. In this post I’m going to share some of the things that I’ve setup in order to get the fastest possible page loads from WordPress.
We’ll be covering general server configuration, Nginx web server configuration, WordPress plugin configuration, and finally use of content distribution networks.
Following on from my recent Linux web server benchmarks and Windows web server benchmarks, I noticed that in general IIS appeared to perform better than all Linux based web servers that I’d previously tested.
As my Linux results were completed in March last year, I’ve run some of the tests again with the most up to date versions of each web server to ensure that the best performance can be achieved.
So let’s find out how Linux and Windows based web servers compare against each other in a static workload speed test.
Following on from my recent Linux web server benchmarks, I’m going to be performing the same tests on all current generations of Microsoft’s IIS web server.
Here I’ll be performing benchmarks against the below versions of the IIS web server and then comparing them against each other to get an idea of which one performs the best under a static workload.
First I’ll discuss how the tests were set up and actually done before proceeding into the results.
Cloudflare is a widely used content distribution network (CDN) which is freely available to help speed up your website by caching various contents at locations around the world.
While I have been taking advantage of the free plan on this website for a number of years I’ve often asked myself “is the Cloudflare Pro plan worth getting?”. At $20 USD per month it costs the same as the server itself. With limited resources available online, I decided to upgrade myself and find out if the pro plan made much of a practical difference to my website.
I’ve performed some basic benchmarks on a number of different file types at different file sizes on this website both on the free plan, and on the Pro plan after I upgraded in August 2016. We’ll take a look at the results and see if any of the Pro features helped speed up load times.
This guide will show you how to increase the security of an Invision Power Board (IPB) installation. We’ll walk through practical examples for you to follow to harden IPB, reducing your attack surface.
There are a lot of insecure default options which unless modified will put you at a higher risk of being compromised by an attacker. Here we will outline what should be modified to increase security of IPB.
I have previously performed a benchmark on a variety of web servers in 2012 and have had some people request that I redo the tests with newer versions of the web servers as no doubt a lot has likely changed since then.
Here I’ll be performing benchmarks against the current latest versions of a number of Linux based web servers and then comparing them against each other to get an idea of which one performs the best under a static workload.
By default Apache will serve web content out over the wire in the clear via HTTP which is insecure. We can increase the security between clients and the web server by using HTTPS. This will encrypt the data transferred between the two and is done by configuring TLS.
Here we will add HTTPS support for our test domain www.example.com, which we previously configured in our virtual host configuration guide.