It's not necessary to use paths for fixtures, so update the docs and
Vagrant install scripts to remove these.
Signed-off-by: Stephen Finucane <stephen.finucane@intel.com>
These can be loaded using the `loaddata` command:
- (.venv)$ ./manage.py loaddata patchwork/fixtures/default_tags.xml
- (.venv)$ ./manage.py loaddata patchwork/fixtures/default_states.xml
- (.venv)$ ./manage.py loaddata patchwork/fixtures/default_projects.xml
+ (.venv)$ ./manage.py loaddata default_tags default_states default_projects
You should also take the opportunity to create a "superuser". You can do this
using the aptly-named `createsuperuser` command:
sudo -E -u vagrant python3 $PROJECT_HOME/manage.py migrate > /dev/null
sudo -E -u vagrant python3 $PROJECT_HOME/manage.py loaddata \
- $PROJECT_HOME/patchwork/fixtures/default_tags.xml > /dev/null
+ default_tags > /dev/null
sudo -E -u vagrant python3 $PROJECT_HOME/manage.py loaddata \
- $PROJECT_HOME/patchwork/fixtures/default_states.xml > /dev/null
+ default_states > /dev/null
sudo -E -u vagrant python3 $PROJECT_HOME/manage.py loaddata \
- $PROJECT_HOME/patchwork/fixtures/default_projects.xml > /dev/null
+ default_projects > /dev/null
echo -e "\n--- Configuring environment ---\n"