From abaaae46730f276638e34f5bf1947acb020b8b8e Mon Sep 17 00:00:00 2001 From: Peter Law Date: Sun, 28 Jan 2018 19:23:59 +0000 Subject: [PATCH 1/2] Indentation --- README.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.rst b/README.rst index e1acb810..22fa5853 100644 --- a/README.rst +++ b/README.rst @@ -5,7 +5,7 @@ django-postgres-extra

- + ==================== =================== **Quality** |QualityBadge|_ From 22b17078a2b84b19034bcc9940948b91df7eb764 Mon Sep 17 00:00:00 2001 From: Peter Law Date: Sun, 28 Jan 2018 19:28:46 +0000 Subject: [PATCH 2/2] Explain how to configure a specific postgres user Not all installs of postgres will have the default user as a superuser, without which developers will see lots of test failures. --- README.rst | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/README.rst b/README.rst index 22fa5853..5643b2be 100644 --- a/README.rst +++ b/README.rst @@ -158,19 +158,30 @@ Working with the code λ virtualenv env λ source env/bin/activate -3. Install the development/test dependencies: +3. Create a postgres user for use in tests (skip if your default user is a postgres superuser): + + .. code-block:: bash + + λ createuser --superuser psqlextra --pwprompt + λ export DATABASE_URL=postgres://psqlextra:@localhost/psqlextra + + Hint: if you're using virtualenvwrapper, you might find it beneficial to put + the ``export`` line in ``$VIRTUAL_ENV/bin/postactivate`` so that it's always + available when using this virtualenv. + +4. Install the development/test dependencies: .. code-block:: bash λ pip install -r requirements/test.txt -4. Run the tests: +5. Run the tests: .. code-block:: bash λ tox -5. Run the benchmarks: +6. Run the benchmarks: .. code-block:: bash