A while ago I “released”limegreen, an application template for making java applications look as good as they can, and function as natively as they can, on OS X, windows and linux.
Anyway, I use it in some of my applications, and I’ve recently added a completely automatic autoupdate feature. It will produce an ATOM file with the version in it and change history, and links for where to get the update files. I choose ATOM, because it meant with the same file I could store information that could be read by a program that needed to know if it should update, as well as allow people to subscribe and be notified of updates in a feed/RSS reader.
I’ve also released a PHP library and wordpress plugin that allows the ATOM file to be read, and version information to be automatically placed on a website. Its what I use to show this, and generated the latest download links on my website. If you’re looking for the PHP library, just download the wordpress plugin and include limegreen.php.
I run several websites / blogs powered off wordpress. In order to back them up I’ve written a unix shell script to do this. It will automatically read the database settings and do a dump of it, as well as copy themes / plugins / uploads.
There are two versions. One will copy files locally, the other allows a remote sync to another server which is compatible with Dreamhost.
The local copy version can be found here: wp-backup.sh Example usage can be seen below. The -t option allows you only to backup a single theme. The -u option allows you to skip backing up uploads.
There is also a version to work with Dreamhost’s free (with hosting) 50GB backup plan than can be downloaded here: wp-remote.sh
./wp-remote.sh /path/to/wordpress email@example.com:backup
where b123456 is your backup user
1) Your wp-config file must be pretty strict in order to be read:
define(‘DB_NAME’, ‘database’); // The name of the database
define(‘DB_USER’, ‘username’); // Your MySQL username
define(‘DB_PASSWORD’, ‘password’); // …and password
2) The directory you’re copying to must already exist.
3) The options/order of the parameters in calling the script is very strict