If you are using Git for version control then it is likely at some point you will have a project with multiple branches of code. The benefit of this is allowing various developers to work on different projects while providing an easier way to merge the code when the developers tasks are completed. One developer may be working strictly on big fixes that could need to be checked in daily while another developer may be working on a project that may take months to complete and git provides a system to merge these code branches together. Below is a quick reference for switching between Git code branches.
I knew that one of my clients web sites is running an older version of WordPress. When I upgrade WordPress I like to know exactly what version is running so I can use something like WinMerge to compare every single file in the WordPress installation to verify specifically what is going to be upgraded. This is useful if you run into any problems you can attempt to only roll back specific files to see if it resolves the WordPress upgrade issue.
Installing the EPEL repository on CentOS Linux is easy to do so the below is simply a reference point if needed by anyone. EPEL stands for Extra Packages for Enterprise Linux and is a community based repository that was created for add-on Fedora Linux packages. There are many cases where installation instructions assume that the EPEL repo is already installed so if you run into an error because of a missing package or dependency package the EPEL repository is a great place to start. Below I have listed the i386(32-bit) and x86_64(64-bit) EPEL repository package list links which will allow you to easily verify that the packages you need are available before installing the EPEL repository. After the EPEL repository package list links there are separate commands listed to install the EPEL repository on 32-bit CentOS Linux 5.X and to install the EPEL repository on 64-bit CentOS Linux 5.X.
My Dell laptop has been claiming there is a hard drive issue for some time however when I reboot and let Windows 7 scan the drive it either doesn’t scan the drive or it scans the drive and still claims there is an issue. I believe the drive doesn’t have any major issues and that it has something else to do with the fact that it is a solid state drive. To get past the problem of Windows always claiming that it needs to scan the drive on reboot I scheduled a scan for the next reboot. Below is information on how to schedule a chkdsk scan on next reboot.
Awhile back I upgraded the “rack” gem on one of our CentOS Linux servers that runs LiteSpeed and Ruby. The upgrade took the rack gem from rack version 1.0.0 to rack version 1.0.1. After upgrading the Rack gem I attempted to visit the site located on the server where the gem was updated only to receive a 503 error from LiteSpeed. During the troubleshooting process I looked at the LiteSpeed error logs and noticed errors that lead me back to the Rack gem I had just updated. Below I describe the error in more detail and what can be done to resolve the issue of rack-1.0.1.