--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/d252a3e0-f8f4-4026-b1eb-9dfd79993618%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hey Dan,
I’ve been working on a project called django_docker_box
(https://github.com/orf/django-docker-box) that might help with this. Docker is pretty good at spinning up various databases without needing to clutter your local machine, spend time configuring authentication or dealing with issues like this.
You might find this helps with you. You can run the entire test suite with it, or you can just spin up a Postgres database and connect to it from your local machine (docker-compose run postgres-db
) with django:django
.
Alternatively you could run:
docker run -p 5432:5432 -e POSTGRES_PASSWORD=django postgres:9.6
And connect to it with postgres:django
on localhost:5432
Mysql can be done in the same way:
docker run -p 3306:3306 -e MYSQL_PASSWORD=django mysql:5.7
Hope this helps,
Tom
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFzonYYhELA0RRpM07KGsYX08CmM09UjeN8vZRovwfmCUTz_2g%40mail.gmail.com.
So, a developer using PostgreSQL doesn't need superuser privileges, but you do to run Django's unit tests, because it will test these contributed postgres operations.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFNZOJMt_w9p2XXaZqyyKPDQycsNAurb9RGea09TfsdpJgNfkQ%40mail.gmail.com.