From 49feb07d679a73a3b9acea11e3e68461ef3770ad Mon Sep 17 00:00:00 2001
From: Jeffrey Forman <jeff@jeffreyforman.net>
Date: Fri, 31 Mar 2017 23:07:32 -0400
Subject: [PATCH] fix documentation to remove incorrect usage of NODB=1 and
 friends

---
 README.markdown | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/README.markdown b/README.markdown
index 35e991c..3107234 100644
--- a/README.markdown
+++ b/README.markdown
@@ -26,7 +26,7 @@ Over the course of developing Binder, it has come to the fore that using a conta
 ### Local Sqlite database ###
 
 ```
-docker run -e NODB=1 jforman/binder:latest
+docker run jforman/binder:latest
 ```
 ### Admin user ###
 
@@ -34,8 +34,9 @@ Default admin user for Binder is 'admin', and password is 'admin' as well.
 
 ### MySQL database ###
 
+If you wish to use a MySQL database, the following structure works:
 ```
-docker run -e DJANGO_DB_HOST="XXXX",DJANGO_DB_PASSWORD="YYYY",DJANGO_DB_USER="binder" jforman/binder:latest
+docker run -e 'DJANGO_DB_HOST=XXXX' -e 'DJANGO_DB_PASSWORD=YYYY' -e 'DJANGO_DB_USER=binder' jforman/binder:latest
 ```
 
 The Django settings.py is configured to accept the following environment
@@ -51,7 +52,6 @@ variables when configuring a MySQL-based backend database.
 Or you can run Binder directly on your host using the Django devserver.
 
 ```
-export NODB=1
 python manage.py migrate
 python manage.py createsuperuser
 python manage.py runserver
@@ -81,7 +81,6 @@ a new initial_data.json file. This uses a local Sqlite database file for
 bootstrapping.
 
 ```
-export NODB=1
 python manage.py migrate
 python manage.py createsuperuser
 ...