• I’m administering a server with about 15 installations of WP on it, each for separate shows on a college radio station, and I’m looking for an easy way to keep them up to date. I’ve kept the blog for my show up to date (with the 2.0.x security changes), but I haven’t had the time to go through and do replace each changed file for every blog setup. Is there any alternative to individually replacing the updated files for each installation?

    We may upgrade to WP 2.1.x at some point as well — would there be an expedited way for doing this to many installations, or is it necessarily a blog-by-blog process?

    by the way, we’ve opted not to use WPMU for a variety of reasons, so I would say don’t bother trying to convince me to switch to that.

    If anyone in a similar situations could comment on their experience as the admin for several separate blogs (each with their own plugins, uploads, etc.), I’d like to hear how you do it. thanks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • I’m in your boat.

    I’m managing WP installations for a radio program that houses blogs for some earth-conscious scientists. They also did not want to use MU, and each scientist has their own WP installation.

    I don’t upload files individually. I just unzip the new installation and upload the whole darn thing in each folder – it is time-consuming.

    Funnily enough, I asked a question on a WP list the other day (about upgrading all the installations), and someone gave me a solution to this…let me see if I can dig up the email.

    EDIT: ah! Even faster than I thought – I *did* keep that email. Here’s what he said:

    “If your client can give you shell access, you could download the archives and uncompress them on the server. Or, if they have SVN installed, you could use ‘svn export –force’ to extract the new version on top of the old one (that’s the fastest, and what I use when I can). Both will be faster than http://FTP.”

    Thread Starter cgang

    (@cgang)

    I guess that’s what I’ll end up doing as well — uploading the whole thing into each folder.

    My first question about WP2.1.x upgrades remains open. Doodlebee, are you still on 2.0.x installations, or at some point did you go through and run the (more complicated) upgrade steps for each installation to get to 2.1? Does anyone else have experience with that?

    We don’t use SVN or anything like that because the server is (for the time being, at least, as our blogs have very low traffic) entirely local on our own Mac OSX 10.4.8 Server machine, so the actual unzipping, overwriting, etc. is quite simple.
    I dread the moment when one of our blogs gets linked to from somewhere very popular, gets thousands of hits quickly, our server goes down, and we have to move hosting for the blogs offsite. (Actually, it’s the moment of the first upgrade I have to do via FTP after we move to another host that I dread. But you get the idea.)

    Doodlebee, are you still on 2.0.x installations, or at some point did you go through and run the (more complicated) upgrade steps for each installation to get to 2.1?

    I’ve upgraded all of my blogs to 2.1. It most certainly wasn’t more complicated than any other upgrade I’ve done – works exactly the same. You backup everything for safety; upload all the files and overwrite the old; run upgrade.php – one step and you’re finished.

    I’ve got 4 of my own blogs – all of them went as smooth as silk. I don’t know where you got the idea it would be more complicated!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘upgrading multiple installations’ is closed to new replies.