> The test_settings and dev_settings should point to a PASSWORDLESS
> database with localhost-only permissions. The production_settings file
> should not be committed. It's the one copied up to the server.
Come to think of it, what I'm screaming about here is three separate
things:
- developer databases should be passwordless.
Whoever steals them steals garbage.
- settings.py should not contain production database passwords
- dev databases should not have the same password as production!
This concludes our public service announcement for today...
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
