I was constantly running into issues with settings.py especially with
INSTALLED_APPS settings. I did some RTFM and figured out something
like this [1]
So I am proposing two settings.py instead of one. The first one is the
default settings.py would be used for development server purposes and
will be referencing the local instance of web. (ie) there are two
places where the django code lives. One being the git/hg source
directory and another in /usr/local/lib/. So when developing, we want
to run the development server from source directory and in deployment
run from /usr/local/lib. There is also another use case where we might
want to debug the deployment server installation.
How two settings.py will help : there will be a settings.py and
deployment.py. When one does a "manage.py runserver" it will pick up
from the settings.py and in deployment scenario, we will specify
"SetEnv DJANGO_SETTINGS_MODULE checker.cc_frontend.deployment" instead
of the current "SetEnv DJANGO_SETTINGS_MODULE
checker.cc_frontend.settings " in the apache config.
Shall I go ahead and make this change ?
[1] http://martinjansen.com/2008/10/20/django-settings-files-for-development-and-production/
--
regards
Suren
Learning < Doing
Learn By doing.
Sounds good. Please document how to use it in the project itself, so
that after cloning, it is easy to find and use. I am going to be able to
find time soon for working on other aspects of this project soon. So can
you either write up how to install the development environment (in case
its not straightforward) or point me to some existing docs?
I am not sure if you might have got notifications from github about
the project being migrated to github but yes, I have currently
migrated all commits to Github. Please take a look at it and let me
know. Also Pk and myself have been working on a one step installation
script sort of item which I will document soon enough, hopefully
before you start working again on it :)
Thanks,
~Suren