tags:

views:

97

answers:

0
Q: 

settings.py DATABASE_USER best practices for Django. Multiple domains/projects.

What are conventions that you recommend when I should use a new DATABASE_USER in settings.py?

Should I use a new postgresql DATABASE_USER for each project database or each site on the same server?

In the case of multiple projects on the same site(domain) should I use a unique DATABASE_USER per each project database?

In the case of multiple projects on different domains but the same server, is there an advantage in using a different DATABASE_USER per database?

Any advice is much appreciated. Thank you.

related questions

Django: Print url of view without hardcoding the url
Django Calendar Widget?
Can the HTTP version or headers affect the visual appearance of a web page?
Project design / FS layout for large django projects
Extending the User model with custom fields in Django
How to generate urls in django
Always including the user in the django template context
Screencasts for Django/Python?
Using Django time/date widgets in custom form
How do I add data to an existing model in Django?
Setup django with WSGI and apache
Altering database tables in Django
Django Templates and variable attributes.
Django ImageField core=False in newforms admin
How can I render a tree structure (recursive) using a django template?
Cleanest & Fastest server setup for Django
Unicode vs UTF-8 confusion in Python / Django?
Does Hostmonster support Django
Specifying a mySQL ENUM in a Django model
Represent Ordering in a Relational Database
updating an auto_now DateTimeField in a parent model w/ Django
Version track, automate DB schema changes with django
Learning Ruby on Rails any good for Grails?
What Hosting Service is best for Django applications?
Class views in Django