On Wed, 2006-08-09 at 12:54 -0700, plungerman wrote:
> dude, that was it. i was importing the module with from myapp import
> my_settings and not doing a relative import as you suggested from
> settings_default import *
To provide some background information, here is the way we process
settings
dude, that was it. i was importing the module with from myapp import
my_settings and not doing a relative import as you suggested from
settings_default import *
thanks!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Grou
On 08/09/06 16:50, plungerman wrote:
> greetings,
>
> what would be the best way to manage the settings files for multiple
> websites that use the same django project? we have a django project
> with 3 applications that we want to use for various clients. through
> apache, we set up the virtual
actually, i mispoke above about the same error. i saw the same error
when i imported the root settings file and tried to assign values by
using root_settings.ROOT_URLCONF = 'myapp.urls' for example. when i as
values like this ROOT_URLCONF = 'myapp.urls ' without prepending it
with root_settings,
hey joe,
thanks for the suggestion. in fact i tried that first and received the
same error as listed above. thinking that it was not so easy, i opted
for the custom default settings manoeuvre described in the
documentation. unfortunately, i saw the same error generated by
mod_python. if you k
Why don't you just create a file called root_settings.py that has all
of the common settings files, and then create a settings file for each
web site that imports root_settings.py?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the G
greetings,
what would be the best way to manage the settings files for multiple
websites that use the same django project? we have a django project
with 3 applications that we want to use for various clients. through
apache, we set up the virtual host stuff for their domain and send all
python/
7 matches
Mail list logo
