Open CloudNiner opened 7 years ago
The fixtures need a bit of tinkering, Django expects them to represent an initial configuration of sorts so they're not flexible for different configurations (You must have the map cells for all of the 200 cities config imported). The documentation is definitely wrong, right now I think the workflow is you have to import the cities, then do import_from_other_instance
to make the map cells (😬), then import from the fixtures. We could bundle cities and map_cells with the historic data but those change more often and the historic data fixture is already pretty huge.
If we wanted to fix this, what would a sensible series of tasks look like?
Steps to reproduce:
./scripts/console django './manage.py loaddata scenarios'
./scripts/console django './manage.py import_from_other_instance staging.somewhere.com API_KEY RCP85 30 5'
./scripts/console django './manage.py loaddata historic_averages historic_baselines'
<-- Crash