On Monday 01 Mar 2010 5:55:41 pm Jirka Vejrazka wrote: > >> Then maybe web server is the best option. In all cases you have to > >> configure something until someday 'runserver' come with ssl support. > > I think that no one would really object if runserver was SSL-aware, >
or you could have an nginx server proxying to the dev server - nginx looks after the ssl and listens on port 443 - runserver does not need to know anything about ssl. And you do not need to restart on code change and you can have print output on the console - in short, have your cake and eat it too. -- regards Kenneth Gonsalves Senior Associate NRC-FOSS http://certificate.nrcfoss.au-kbc.org.in -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
