Upgrading to Dogwood is complicated, because we have to make two intermediate stops along the way: once at the end of Django 1.4 to migrate the databases using South, then to the beginning of Django 1.8 to apply --fake-initial migrations. Then we can upgrade to the Dogwood release that we actually want.
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| callback_plugins | Loading commit data... | |
| edx-east | Loading commit data... | |
| group_vars | Loading commit data... | |
| library | Loading commit data... | |
| roles | Loading commit data... | |
| vagrant | Loading commit data... | |
| ansible.cfg | Loading commit data... | |
| create_django_ida.yml | Loading commit data... | |
| create_role.yml | Loading commit data... | |
| ec2.ini | Loading commit data... | |
| ec2.py | Loading commit data... | |
| edx_sandbox.yml | Loading commit data... | |
| inventory.ini | Loading commit data... | |
| log_server.yml | Loading commit data... | |
| run_role.yml | Loading commit data... | |
| security.sh | Loading commit data... | |
| security.yml | Loading commit data... | |
| vagrant-analytics.yml | Loading commit data... | |
| vagrant-cluster.yml | Loading commit data... | |
| vagrant-devstack.yml | Loading commit data... | |
| vagrant-fullstack.yml | Loading commit data... |