On Wed, Sep 24, 2008 at 9:15 AM, phillc <[EMAIL PROTECTED]> wrote: > > So for all my other django projects, i have used local_settings in the > past for things that need to be specific to a system... as in the file > that is distributed as a template for version control reasons.... > > I noticed that that is what satchmo has started to do... makes sense > to have email host and caching options in this local file... (which is > where i also keep my database settings)... > > but im curious, why are things that are project specific in this > local_settings file instead of settings, like: things that rely on > os.path (the logging stuff), the SHOP_BASE var, and the default URLS, > the custom whatever modules... > > that kinda thing... shouldnt my dev environment look the same as my > production? >
It should, and anything that's crept into local_settings which should be in settings really should be moved into the master settings file. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
