Techblog Archive

A short introduction to the branching model used by MD Systems, which is based on three branches, master, staging and production.

Drupal 7 defaults to InnoDB now out of the box. This has many advantages, including being much more stable if your server crashes and support for transactions. However, out of the box, InnoDB (and MySQL in general) can be very slow.

It often happens that you commit some changes and instantly see that you forgot to add a new file, wanted to add a line to the changelog, or just noticed a typo in a comment that you'd like to have in the same commit. Or another use case is when working on contrib issue and want to create a format-patch patch so that you are automatically credited as the author but want to avoid having multiple commits in the patch.

The default location (usually a branch on a remote) for pushing and pulling is called upstream in Git. There are multiple ways to specify the upstream. This tutorial explains three of them.

Once a project has been assigned to a group, that selection can not be reverted or changed. The only way to do it is with a manual query.

Interactive rebasing allows to quickly delete commits, merge multiple commits together or rename commit messages.

There are a number of typical scenarios which slow down a site. This tutorial attempts to explain a few and provide tipps to fight them.

There are many possible causes for a slow site. Instead of poking around blindly, it is recommend to do some performance profiling.

When I work on fixing bugs or adding new features I often add debug statements all over the place to debug something and find out where it goes wrong. Before I can then create a patch or commit the changes, I need to clean up the working tree first. Although a git diff can already help a lot, it's still tedious work to open the different files, look for debug statements and remove them. Luckily, git can do much more than just point out where the changes are.