enewe101
commented
9 years ago Ok, the app is ready for upgrading to Django 1.7. Next time you commit to the branch your working on, checkout master and go do the upgrade instructions below. Afterward you can go back to your branch, merge in master, and continue working using Django 1.7 (as explained below). Here we go:
$ git pull$ git checkout master- Open up
src/digidemo/settings.pyand delete or comment the lineFIXTURE_DIRS = (os.path.join(PROJECT_DIR, 'data/fixtures'),). That should be around line 114, although our settings files can differ somewhat. $ sudo pip install Django --upgrade- Wipe your digidemo database by heading into mysql, and doing
mysql> drop database digidemo; create database digidemo;then exit mysql - in
digidemo/srcrun$ python manage.py migrate - run the tests to make sure it went well: in
digidemo/srcrun$ python manage.py test
If the tests went well, you can go back to the branch you were working on, merge in master, and continue working, like this:
$ git checkout branch-you-were-working-on$ git merge master
Post here if you run into problems!
mlhuish
We've been putting off the upgrade to Django 1.7 (the latest version), because upgrading breaks the app. But now is probably a good time, because we need one of the features introduced in 1.7: migrations.
Migrations are used when changes are made to models, in order to apply those changes to a database that already has data. Migrations tell the database how to to make changes to its structure while preserving the existing data.
Now that we have a live server, and are finding the need to evolve our models, it makes sense to go ahead and migrate.
To make the app work with 1.7, a very small change needs to be made to how the test data fixture is loaded during testing. You'll need to toast your database and rebuild it after upgrading. I'll post instructions in this issue soon. It should be possible for the code base to be compatible with versions 1.6 and 1.7 while we make the shift.