summaryrefslogtreecommitdiff
path: root/requirements-dev.txt
diff options
context:
space:
mode:
authorStephen Finucane <stephen@that.guru>2018-09-13 12:13:35 -0600
committerStephen Finucane <stephen@that.guru>2018-10-10 10:17:36 +0100
commitc21990a8d7bfd363fb885879947e794f4a1fa04b (patch)
treead419c57cd61e4f14c5b6f5abbd8e3ed816f1a4d /requirements-dev.txt
parentae13c6ead782b7ef285c9d35042614e86c221a9c (diff)
downloadpatchwork-c21990a8d7bfd363fb885879947e794f4a1fa04b.tar
patchwork-c21990a8d7bfd363fb885879947e794f4a1fa04b.tar.gz
Add support for 'django-dbbackup'
'parsemail' and 'parsearchive' are slow. When messing with models and migrations, it can be very useful to backup the database in its current state and restore it if/when you mess up. Currently, we've documented how to do this via some commands run in the shell of the container, but we can do things easier via an application designed for this purpose: 'django-dbshell'. Signed-off-by: Stephen Finucane <stephen@that.guru>
Diffstat (limited to 'requirements-dev.txt')
-rw-r--r--requirements-dev.txt1
1 files changed, 1 insertions, 0 deletions
diff --git a/requirements-dev.txt b/requirements-dev.txt
index b0cdd0d..ed98c30 100644
--- a/requirements-dev.txt
+++ b/requirements-dev.txt
@@ -3,4 +3,5 @@ Django==1.11.15; python_version < '3.0' # pyup: ignore
djangorestframework==3.8.2
django-filter==2.0.0; python_version >= '3.4'
django-filter==1.1.0; python_version < '3.0' # pyup: ignore
+django-dbbackup==3.2.0
-r requirements-test.txt