This looks like it'll be a problem: We don't *always* want to fake migrations for djcelery. It has valid migrations that need to be run, especially on a new VM with a blank DB