Administration of EDD

Common Maintenance/Development Tasks

Some of these sample commands will only work as written at JBEI, but should serve as useful examples for common development tasks. Directions assume that Docker containers are already running in the development environment.

Run automated tests

Tests must run with an edd-core image that is built with TARGET=dev. This is the default when manually building, but is not the default for images pushed to Docker Hub. Run tests with:

docker-compose exec http pytest

Test email configuration

Use the Django management command sendtestemail (docs).

docker-compose exec http /code/ sendtestemail

Create an unprivileged test account

Use the Django management command edd_create_user, which is based on the createsuperuser (docs) command. Instead of making a superuser, it creates an unprivledged user, and auto-verifies that user’s email address.

docker-compose exec http /code/ edd_create_user

Dump and Restore database contents

Create a database dump and save it to a file using pg_dump. The command below connects to the postgres server at (-h), and the database edd (-d), with the user/role jane (-U), and saves output to the file dump.sql (-f).

pg_dump -h -d edd -U jane -f dump.sql

To restore this dump in a testing database, use the edd-postgres Docker image. Configure the container with a new, empty volume loaded at /var/lib/postgresql/data, and mount the dump.sql file to one at /docker-entrypoint-initdb.d/200-data.sql. When the container launches, it will initialize a new, empty database for EDD, and restore data from the dump file before making the database available for use.

Rebuild Solr indices

Use the Django management command edd_index. Pass in the --force flag to run a full re-index even if it appears each index contains the correct data.

docker-compose exec http /code/ edd_index

Upgrading EDD

The simplest way to update EDD is to pull the newest image, then run docker-compose up -d. This will re-create containers using the new image.