As currently written, the PGD cookbook creates its own database and populates that database with a small number of proteins for the purposes of testing.
The cookbook should be modified to allow the usage of an external database that already exists. This would require the disabling and possibly removal of the code that populates the database, and rendering the database creation code as optional.
The cookbook should also run the Django app tests as part of the kitchen converge process, but I do not know if you want that in a separate issue.
As currently written, the PGD cookbook creates its own database and populates that database with a small number of proteins for the purposes of testing.
The cookbook should be modified to allow the usage of an external database that already exists. This would require the disabling and possibly removal of the code that populates the database, and rendering the database creation code as optional.
The cookbook should also run the Django app tests as part of the kitchen converge process, but I do not know if you want that in a separate issue.