>
> Sorry, meant to answer this. It is a long story but I can't use runserver
> at the moment. I'm developing on Windows, updating from the repo on a spare
> Ubuntu server with no GUI and using fab deploy to get it across to the
> production server - also sans GUI.


Ah, I figured it was something like that. Well even if you can't use
runserver you ought to find some way to log verbosely for debugging. The
most reasonable way would probably be to use the DJANGO_SETTINGS_MODULE
environmental variable to point to an alternative settings.py with
DEBUG=True. You'll may need to set up logging
<https://docs.djangoproject.com/en/1.8/topics/logging/> manually in order
to get the verbose output.

On Sat, Aug 15, 2015 at 2:46 AM, Mike Dewhirst <mi...@dewhirst.com.au>
wrote:

> On 15/08/2015 10:45 AM, Ryne Everett wrote:
>
>>     Thanks Ryne, unfortunately no. Nothing in the supervisor, gunicorn
>>     or nginx logs. Are there any others?
>>
>>
>> Oh, I didn't realize this was a production environment. Do you
>> experience the same thing using runserver?
>>
>
> Sorry, meant to answer this. It is a long story but I can't use runserver
> at the moment. I'm developing on Windows, updating from the repo on a spare
> Ubuntu server with no GUI and using fab deploy to get it across to the
> production server - also sans GUI.
>
> TLDR: Before wheels I could get anything working on Windows by using Chris
> Gholke's nightly binaries. But now it seems I need a Microsoft C++
> compiler. I'm thinking I now need to find some brainspace for Virtualbox so
> I can run a Linux GUI for development. And then move acres of stuff across.
> I feel depressed just thinking about it. I'm locked into Windows for
> various reasons.
>
> Thanks again
>
> Mike
>
> Also, where are you getting
>
>> the "uninformative "there has been an error" or similar"?
>>
>> On Fri, Aug 14, 2015 at 8:00 PM, Mike Dewhirst <mi...@dewhirst.com.au
>> <mailto:mi...@dewhirst.com.au>> wrote:
>>
>>     On 14/08/2015 11:59 PM, Ryne Everett wrote:
>>
>>         Â  Â  Is there a rule which says index.html cannot extend
>> base.html?
>>
>>
>>         No. That's what I do.
>>
>>         Â  Â  It does seem to work - at least until I try and use an
>>         <img> tag. It
>>         Â  Â  then barfs with an uninformative "there has been an error"
>>         or similar.
>>
>>
>>         I suspect a more detailed error message will be necessary to
>>         figure out
>>         what's going wrong. I'm assuming this message is in the logs?
>>
>>
>>     Thanks Ryne, unfortunately no. Nothing in the supervisor, gunicorn
>>     or nginx logs. Are there any others?
>>
>>
>>         On Fri, Aug 14, 2015 at 9:14 AM, Mike Dewhirst
>>         <mi...@dewhirst.com.au <mailto:mi...@dewhirst.com.au>
>>         <mailto:mi...@dewhirst.com.au <mailto:mi...@dewhirst.com.au>>>
>>         wrote:
>>
>>         Â  Â  Is there a rule which says index.html cannot extend
>> base.html?
>>
>>         Â  Â  It does seem to work - at least until I try and use an
>>         <img> tag. It
>>         Â  Â  then barfs with an uninformative "there has been an error"
>>         or similar.
>>
>>         Â  Â  The base.html blocks all render nicely - but not the
>> content.
>>
>>         Â  Â  Could it be that I need a plain and self-contained
>>         index.html page
>>         Â  Â  which is not a Django template?
>>
>>         Â  Â  Thanks
>>
>>         Â  Â  Mike
>>
>>         Â  Â  --
>>         Â  Â  You received this message because you are subscribed to
>>         the Google
>>         Â  Â  Groups "Mezzanine Users" group.
>>         Â  Â  To unsubscribe from this group and stop receiving emails
>>         from it,
>>         Â  Â  send an email to
>>         mezzanine-users+unsubscr...@googlegroups.com
>>         <mailto:mezzanine-users%2bunsubscr...@googlegroups.com>
>>         Â  Â  <mailto:mezzanine-users%2bunsubscr...@googlegroups.com
>>         <mailto:mezzanine-users%252bunsubscr...@googlegroups.com>>.
>>         Â  Â  For more options, visit https://groups.google.com/d/optout.
>>
>>
>>         --
>>         You received this message because you are subscribed to the Google
>>         Groups "Mezzanine Users" group.
>>         To unsubscribe from this group and stop receiving emails from
>>         it, send
>>         an email to mezzanine-users+unsubscr...@googlegroups.com
>>         <mailto:mezzanine-users%2bunsubscr...@googlegroups.com>
>>         <mailto:mezzanine-users+unsubscr...@googlegroups.com
>>         <mailto:mezzanine-users%2bunsubscr...@googlegroups.com>>.
>>         For more options, visit https://groups.google.com/d/optout.
>>
>>
>>     --
>>     You received this message because you are subscribed to the Google
>>     Groups "Mezzanine Users" group.
>>     To unsubscribe from this group and stop receiving emails from it,
>>     send an email to mezzanine-users+unsubscr...@googlegroups.com
>>     <mailto:mezzanine-users%2bunsubscr...@googlegroups.com>.
>>     For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Mezzanine Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to mezzanine-users+unsubscr...@googlegroups.com
>> <mailto:mezzanine-users+unsubscr...@googlegroups.com>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to