Thanks Malcolm.
It is the case.
Instead of relying on the DJANGO_SETTINGS_MODULE which was there in
the /etc/profile
i have used the below code (taken from
http://superjared.com/entry/django-and-crontab-best-friends/
& also mentioned by peteDK)
-
from django.core.management import setup_e
On Mon, 2009-01-26 at 19:46 -0800, Rama Vadakattu wrote:
> i configured the DJANGO_SETTINGS_MODULE in /etc/profile.this means
> that it is a system wide environmental variable and can be used every
> where.
Cron jobs are run in a very limited environment by default, for security
reasons. That inc
i configured the DJANGO_SETTINGS_MODULE in /etc/profile.this means
that it is a system wide environmental variable and can be used every
where.
On Jan 26, 8:09 pm, Daniel Roseman
wrote:
> On Jan 26, 1:55 pm, Rama wrote:
>
>
>
> > i have a standalone python script which uses a django module. i n
Hi
I have had some problems with that myself. Don't know if this is any
help, but here we go.
i have created a file cron.py that i have placed in the exact same
directory as my settings.py file.
then at the beginning of my cron.py:
from django.core.management import setup_environ
import settings
On Jan 26, 1:55 pm, Rama wrote:
> i have a standalone python script which uses a django module. i need to
> schedule that script using crontab.
> while doing this i encountered the following problem
>
> 1) the above standalone python script which uses django module is running
> properly on the
i have a standalone python script which uses a django module. i need to
schedule that script using crontab.
while doing this i encountered the following problem
1) the above standalone python script which uses django module is running
properly on the terminal.
( DJANGO_MODULE_SETTINGS are
6 matches
Mail list logo