How should we use local svn with the new upgrade system?

  • NB. I’m a Subversion noob, just learning the ropes (using Versions.app currently).

    This is mostly a question about workflow, subversion and auto-updating WordPress on the live server.

    Normally my live site is mirror of a local dev copy (managed with subversion), and each time WP releases a new version, I update my local copy, test and tweak the themes/plugins as necessary, then upload (svn export) that to the live server.

    Now that there’s a handy one-click upgrade method available within the WP admin area, my live copy can in theory be more up-to-date than my local working copy! Version control chaos ensues.

    Can anyone offer some advice on how to integrate WP auto-updating features into a simple svn workflow?

    Should I just svn manage my theme folder and let WP handle the app updates server-side?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator Samuel Wood (Otto)

    (@otto42)

    www.remarpro.com Admin

    How you do it is really up to you, but I’ve never bothered with doing an svn export and then uploading the stuff. Get shell access to your box and just run svn up on it directly. ??

    The auto-updater only gets the latest ZIP file, BTW. It doesn’t do up-to-the-minute stuff, unless you’re running trunk, in which case it gets the nightly build.

    Thread Starter junap

    (@junap)

    All I’m after is the official point releases and plugin updates, rather than bleeding edge stuff. The various client sites I code for don’t usually have shell access either.

    I’m going to go with just managing the theme folder under svn and let WP update itself on the server for now.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘How should we use local svn with the new upgrade system?’ is closed to new replies.