I’ve been looking into Gitflow recently, it’s an interesting set of scripts to facilitate a successful git branching model which some of the people I work with rave about.
In the end I’ve decided I don’t like the tool or the model, though both are interesting.
In a busy team, with ongoing testing I often find we have a production version of the site, a version under test, and another version being actively developed.
In fact it can be less clear than this if release planning isn’t a priority, some teams simply churn out releases some of which get tested and eventually released.
This can lead to developers being unsure which update hooks have actually run on production (or will have run by the time the next release goes live).
In this case it’s important for somebody to manually review all install files that have been edited and check that we don’t end up releasing update hooks that have been edited after they have been run.
This script fires up a visual diff tool for the changed files.
This script makes sure the dev site is clean, emails a log summary of updates about to be applied, updates the site and emails me so I know what changed.
I’m using this on a dev site which is periodically updated to the latest master for testing.
I’ve been working on a project for a while on my main dev machine, but needed to run it on my laptop too.
Usually copying a site across is quick but this time I re-installed the OS too, everything went OK except for some reason I couldn’t log in to my drupal site.
Eventually I noticed that while the site appeared to be working, every page was being served with a 404 header.