Have you ever wanted to review past updates or roll back an update that broke your sites or negatively affected some aspect of your server’s operations? Well, you can accomplish this easily by using the yum history command.Continue reading “How To Use The YUM History Command”
Reading Time: 2 minutesThe Liquid Web CDN improves your website’s load time by taking all of your site’s media (pictures, music, etc.) and distributing it to a worldwide caching network. When a visitor reaches your CDN-enabled websites they will receive the basic elements (text, framework code, etc.) from your server as normal, but all the media will be handled by the CDN’s worldwide network of caching servers (also referred to as “nodes”).
Because media files are almost always much larger than text elements, the CDN takes a lot of the workload from your dedicated server. Please note that the Liquid Web CDN is only for use with media files and does not handle databases or other server-side functions. Database activity and other functions will continue to be handled by your server.
It is also important to note that adding CDN services to your server requires modifications to your website’s code. If you are using a Content Management System (CMS) such as WordPress, Drupal, Joomla, etc. then these changes can be easily made using the CMS software itself. If your website was custom-built and does not have a CDN option in the CMS interface, you will need to consult your site’s developer for assistance in implementing CDN code changes. Continue reading “What is a CDN? An Overview”