Hi guys,
Thanks everybody for all the answers, really helped me.
I *SOLVED the problem.*
The problem was I was calling custom enviroment variables into my
settings.py . So that enviroments variables exists on bash (thanks to
.bashrc) but not in cron ( thanks Branko Majic ) so manage.py failed
On 7/02/2013 12:39am, Jesús Lucas Flores wrote:
Hey guys,
I need a little bit help with a custom manage.py command called *test*
There is already a manage.py subcommand called test. Might be an idea to
rename your custom command and try again.
Just a thought ...
I am using it in a vi
I think this has to do with not mentioning the proper settings file.
manage.py goes to the settings and checks all the installed apps for any
custom commands, but if you haven't set proper settings file then it would
not recognize those commands. You can either set the environment variable
to D
On Wed, 6 Feb 2013 05:39:55 -0800 (PST)
Jesús Lucas Flores wrote:
> Hey guys,
>
> I need a little bit help with a custom manage.py command called *test*
>
>
> I am using it in a virtualenv on a shell script *script.sh*,
>
> The script.sh works well out of the cron and Wihiout activate the
4 matches
Mail list logo
