OK .. I dislike that approach but I guess I can live with it. It does bring up a few other questions:
How do I deploy my store? 1- Have a separate local_settings? 2- Deploy without a local_settings? 3- Edit local_settings and/or settings to deploy? local_settings has LOCAL_DEV = True Would I ever want to set LOCAL_DEV to False? Shouldn't settings set the CACHE_ variables? How about TEMPLATE_DIRS ? Why does DIRNAME get redefined in local_settings? Thanks for the tutorial Karl On Feb 2, 6:42 am, Günter Walser <[email protected]> wrote: > In one you put the settings which are most likely not to change, in the > other the one which will change per instalation, user or whatever else. > > Example: > > In settings.py you put all the things which are common for your development, > test and production environment (configuration). > In local_settings.py you put the things which will be overriden for each > environment, like the database you use, if it is in debug mode. > > Rgds > günter > > -----Ursprüngliche Nachricht----- > Von: [email protected] [mailto:[email protected]] > Im Auftrag von kbochert > Gesendet: Montag, 02. Februar 2009 15:38 > An: Satchmo users > Betreff: settings -- local settings > > What purpose is served by having separate settings.py and local_settings.py > files? > > Karl --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
