My Development Setup/Flow

Developers seem to love to hear about how other developers work, so I thought I’d try to capture my entire environment, from end to end, in a single post. This will change (has changed) over time and depending on the project/company/whatever, but this is how things are for me right now. A couple of points up front:

  • I work for Automattic, so a lot of this is influenced by our internal policies/security/workflow.
  • I don’t always use all components of this “system”. I’ll try to detail when I do/don’t use certain parts of it as I go.

OK, here goes.

Note: This turned into a little bit of a summary of how we work internally at Automattic as well. Oh well, maybe it’ll provide some inspiration, I think we do some pretty cool things.


Managing Your WordPress Install With Subversion (Safely)

There are a number of different ways to manage a WordPress installation, everything from not actually managing it yourself ( can take care of it for you if you like) through to manually managing things via FTP. I’m going to look at my preferred method, which I think provides a few things that other methods don’t necessarily give you.

  1. Control: this method puts you in charge (which also means it’s your responsibility to keep things up to date).
  2. Safety: if you consistently manage your WordPress install using this method, then you’re in a pretty good position to avoid a lot of problems.
  3. Simplicity: WordPress updates quite often (minor releases at least every month generally). This system means that you can generally update when a new version comes out in a few minutes at the absolute most.

What is this magic system you ask? In a word: Subversion.