After spending many hours working on your website, you want to ensure that it stays up and running. There are many tools available to monitor the status of your website and infrastructure such as system logs for identifying bugs and monitoring how much traffic is being received. Then there are third party services like StatusCake and Uptime Robot that ping your servers frequently and attempt HTTP requests and compare the result to predefined rules.
Running your website’s administration panel on a private network can help increase security along with increase your website’s performance if you perform demanding administrative tasks. This post will cover the idea of running a website admin panel on a private network instead of making it public while still having full control over the public site’s data. I haven’t yet done this in a production environment, but the site I’m currently working on will most likely implement a method similar to the one below.
Nearly every website implements some sort of pagination of data. Pagination is the process of splitting large sets of information into multiple pages (i.e. search results, emails, etc). In most cases for pagination to work, the total number of items for the dataset must be calculated to know total number of pages. This is commonly done by performing two SQL queries, one to receive the data for the current page and another to count the total number of rows to later calculate the total number of pages.
Uploading website files routinely can become a chore, and no one wants that. Queue a deployment script, at the very least, it’s a script that uploads files to the server, but can be as advanced as verifying files once uploaded, run code tests, and update database structures along. There are two different methods to run a deployment script. First being automated deployment with continuous integration systems to a staging or production servers.
When you want to backup your Evolution calendar, mail, memos, and address book, you have to open up Evolution, go to the file menu, and then follow a few steps before the backup is saved to your computer. This is generally fine if you backup infrequently and you’re able to remember to backup the application every time you perform a computer backup. For me, I prefer automating as much of the backup process as possible.