Dyomedea
/
binder
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

fix documentation to remove incorrect usage of NODB=1 and friends

This commit is contained in:
Jeffrey Forman 2017-03-31 23:07:32 -04:00
parent 4c7ed9beb6
commit 49feb07d67
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.markdown
View File

@ -26,7 +26,7 @@ Over the course of developing Binder, it has come to the fore that using a conta
### Local Sqlite database ### ### Local Sqlite database ###
``` ```
docker run -e NODB=1 jforman/binder:latest docker run jforman/binder:latest
``` ```
### Admin user ### ### Admin user ###
@ -34,8 +34,9 @@ Default admin user for Binder is 'admin', and password is 'admin' as well.
### MySQL database ### ### 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 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. Or you can run Binder directly on your host using the Django devserver.
``` ```
export NODB=1
python manage.py migrate python manage.py migrate
python manage.py createsuperuser python manage.py createsuperuser
python manage.py runserver python manage.py runserver
@ -81,7 +81,6 @@ a new initial_data.json file. This uses a local Sqlite database file for
bootstrapping. bootstrapping.
``` ```
export NODB=1
python manage.py migrate python manage.py migrate
python manage.py createsuperuser python manage.py createsuperuser
... ...