Hi Andréas,

Andréas Kühne wrote:

> The main thing is that when you start runserver it continuesly checks for
> changes in your .py files. So if you change a file, you get a reload. This
> shouldn't be running on a production environment. 
> Another thing is that runserver also serves static files - something that
> you don't want your application server to do in production - that is better
> handled by a webserver.

Okay, that's fine for me and my private / local application.

> If only you are looking at the application that isn't a problem, but I
> wouldn't allow it to be accessible to the Internet....

That's clear. No forwarding from/to any public IP is existing.

> 
> Regards,
> 
> Andréas
> 

Best regards,

Erik

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/1416b1a8-5e52-428f-c258-096ffe12094b%40rdsoftware.de.
For more options, visit https://groups.google.com/d/optout.

Reply via email to