this is all hypothetical since I haven't migrated any apps yet, but
why would we want to have separate settings files if only the database
config would change? To answer your question: I would ideally want to
support these scenarios :
1. developer running app on local machine
2. developer running app on a shared dev server (some of our databases
are so huge it is a pain to set up locally)
3. app on a stage server
4. app running on prod server
I guess everyone solves this by making separate settings files. I
still find it unappealing to put environment settings (like
user/pass., etc) into the code repository, but hey.
On 5/9/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>
> On 5/9/06, Kumar McMillan <[EMAIL PROTECTED]> wrote:
> > Also, at my company we use sandboxed
> > postgres (every user has his own database, named $USER) on our main
> > dev server for better isolation. This means we pretty much have to set
> > database settings as envionment variables.
>
> Sorry, I'm not quite following. Are you running django on each
> developer's local machine, or also on the central server?
>
> What's wrong with having a distinct settings.py for each
> developer/environment?
> Perhaps it'd be useful to have settings.py import * from another
> module (perhaps ${user}-settings.py)?
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
