Checking that Django has all migrations.

Kit Sunde
Kit Sunde
Oct 25, 2016 · 1 min read

All of our project are setup with continuous deployment on CircleCI. An occasional source of errors has been caused by missing model migrations because the migration wasn’t committed.

There’s a simple solution by adding a migration check before deploying:

src/backend/ makemigrations --check --dry-run --settings=conf.settings.test > /dev/null || echo "Missing migrations."

We’re using conf.settings.testwhich has sqlite3 since Django will attempt to connect to your database and error out if it isn’t available even on --dry-run

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store