Comments on: The RedMonk IT Report: Automated WordPress Updating

By: ckunte.com | Upgrading WordPress with svn

ckunte.com | Upgrading WordPress with svn — Sun, 23 Mar 2008 17:19:01 +0000

[...] Automated WordPress Updating. [...]

By: Tarski · Tarski in Polish, 2.1 Plans, Subversion

Tarski · Tarski in Polish, 2.1 Plans, Subversion — Sun, 06 Jan 2008 13:52:19 +0000

[...] with the minimum of effort. There are a bunch of tutorials out there on this subject (for example, this one). If people are interested I can write up a quick tutorial on how I keep things up to date on this [...]

By: ceejayoz

ceejayoz — Mon, 06 Aug 2007 12:33:11 +0000

This is very, very useful. Thank you! My WordPress and Tarski installs are running off an hourly SVN fetch now.

By: WordPress: Automatically Update Your Blog » D’ Technology Weblog: Technology News & Reviews

Wed, 25 Apr 2007 11:01:15 +0000

[...] here) installed and you’re running WordPress on a *nix server, check out — Red Monk and Aaron Brazell’s bash files that help you automatically update all of your [...]

By: The WordPress Podcast » Episode 23: WordPress 2.2 delayed, GSoC workers, Aaron Brazell

Tue, 24 Apr 2007 14:53:53 +0000

[...] Your BlogIf you have Subversion installed and you’re running WordPress on a *nix server, both Red Monk and Aaron Brazell have bash files to help you automatically update all of your WordPress [...]

By: Changing SVN Repositories at Scattered

Changing SVN Repositories at Scattered — Fri, 20 Apr 2007 02:31:09 +0000

[...] about using the technique of updating wordpress through SVN but it just dawned on me that the instructions I (and many others) used committed us to the 2.1 trunk. And since 2.2 is a few weeks away I’m [...]

By: Alex

Alex — Mon, 09 Apr 2007 04:16:41 +0000

Rick, if you read the announcement carefully you’ll see that only the packaged download was corrupted, not the files in SVN. In fact, the files in SVN are much safer as lots of developers access them, review changes and receive e-mail notifications when they are updated.

By: Automated WordPress Updating at Scattered

Automated WordPress Updating at Scattered — Sun, 08 Apr 2007 07:55:02 +0000

[...] finished setting up all the blogs I host to update wp using SVN. What a relief it is to have all those installs up-to-date and knowing I’ll never have to [...]

By: SVN as a “Package Management” Tool | alexking.org

SVN as a “Package Management” Tool | alexking.org — Fri, 06 Apr 2007 13:08:02 +0000

[...] Steve and I even agree on this one. [...]

By: rick gregory

rick gregory — Sat, 10 Mar 2007 02:24:51 +0000

Hmm…

“…2.1 is only getting bug fixes now - the active development is on trunk. as a result, it’s just the stable code with fixes applied…”

Does this include incremental releases like 2.1.1 and 2.1.2? I ask because 2.1.1 contained a security exploit according to the Wordpress blog:

“Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately.”

Of course if your process is automated you’d pick up 2.1.2 as soon as it was available, but still…