Backups seem to be a constant pain for just about everyone. It’s something we know we should do, but somehow never get around to actually doing. Since switching to Wordpress on this site, things have been different though.
One of my many installed wordpress Plugins is the Wordpress Backup plugin. It runs once a day and makes a complete backup of my wordpress database (with all these precious posts) and sends it in a mail to my Gmail-account.
I’ve been moving a fairly large part of my private mail to my Gmail account. Gmail do have some amazing features for searching, labeling and handling mail and the virtually unlimited storage is also pretty cool - Much cooler than keeping a huge mail-archive on an IMAP-server or having it on a local fragile hard disk.
One of the more recent things I’ve started using GMail for is backups of this site. With the wp-db-backup plugin for Wordpress a backup of the entired database is mail to my gmail account every 24 hours and using filters I’m applying a ”backup”-label and auto-archiving it (and avoiding noise in inbox).
Gmail from Google is usually great, but it does have some bug-like features.
One of the most annoying is when your inbound mail is tagged with a label and should have been auto-archived, but is caught by their spam filter and placed in the spam folder. Discovering and finding the mail in the spam folder is easy, but when you tell Gmail, that the mail isn’t spam, it doesn’t pop in to the archive (where the filter-rule should have put it). It pops back into the inbox, and you can then archive from there.
A number of podcasts and websites have mentioned that you can get your Gmail SSL encrypted by just adding a small s in the url (from http:// to https:// in the url). Cool. But wait there’s more… it seems to work for Google Docs and Google Reader too. While I doubt the usefulness of an encrypted RSS Reader, there’s certainly a great vaule in having encrypted access to documents used with Google Docs.
GMail and other web applications have adopted a new technique coined Ajax (by Adaptive Path). It brings web applications a step away from the stateless web and closer to real applications. It’s harder to built applications with the applications, but it’s hot – and the most recent release of Rails (for Ruby) promises to make it much easier to do Ajax applications. Before you do too many Ajax applications, do think for a second. Tadalist is a great example which could have been so much better with less Ajax code. The application rocks in a browser – if you’re at a full computer where the browser knows about and fulfil the requirements posed by the Ajax technique.